From: Ingo Molnar <mingo@kernel.org> To: Yinghai Lu <yinghai@kernel.org> Cc: Borislav Petkov <bp@alien8.de>, Matt Fleming <matt.fleming@intel.com>, "H. Peter Anvin" <hpa@zytor.com>, Bjorn Helgaas <bhelgaas@google.com>, Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@redhat.com>, Jiri Kosina <jkosina@suse.cz>, Borislav Petkov <bp@suse.de>, Baoquan He <bhe@redhat.com>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, "linux-efi@vger.kernel.org" <linux-efi@vger.kernel.org>, "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>, Kees Cook <keescook@chromium.org> Subject: Re: [PATCH v2 04/15] x86, kaslr: get kaslr_enabled back correctly Date: Wed, 4 Mar 2015 21:00:00 +0100 [thread overview] Message-ID: <20150304200000.GB6276@gmail.com> (raw) In-Reply-To: <CAE9FiQWKNDgzJtDVV34e7vWTu7LtqdDKB4KiN1RZwcZrX70zSA@mail.gmail.com> * Yinghai Lu <yinghai@kernel.org> wrote: > On Wed, Mar 4, 2015 at 2:16 AM, Borislav Petkov <bp@alien8.de> wrote: > > On Wed, Mar 04, 2015 at 12:00:37AM -0800, Yinghai Lu wrote: > >> commit f47233c2d34f ("x86/mm/ASLR: Propagate base load address calculation") > >> is using address as value for kaslr_enabled. > >> > >> That will random kaslr_enabled get that set or cleared. > >> Will have problem for system really have kaslr enabled. > >> > >> -v2: update changelog. > > > > This is still not good enough. Please do this: > > > > In commit f47233c2d34f we did A. The problem with that is B. Change the > > code to do C. > > > > Now you only have to fill out the A,B and C variables with the > > respective text which is understandable even for people who don't know > > this code. > > > > I don't know, that is trivial and obvious. The fix might be obvious, the effects of the bug are not obvious at all, as you yourself show that you don't understand your own change, which is evident from the changelog you've written: > Please check if it is ok: > > Subject: [PATCH v3] x86, kaslr: get kaslr_enabled back correctly Missing capitalization. > > commit f47233c2d34f ("x86/mm/ASLR: Propagate base load address calculation") > is using address as value for kaslr_enabled. Missing capitalization. Do you really expect maintainers to fix up every single sentence of yours?? > That will get wrong value for kaslr_enabled, so have problem for > system really have kaslr enabled. This sentence does not parse, nor is it correct: the bug isn't just triggering on systems that want to have kaslr enabled - but also on bootloaders that happen to pass in a kaslr boot parameter but have the switch value disabled... You also need to point out the important fact that bootloaders that don't try to use the kaslr extension (i.e. that don't use SETUP_KASLR) work just fine - this is why the bug was not noticed to begin with, i.e. the overwhelming majority of systems out there. > This patch change to using early map and accessing the value. s/change to using/changes the code to use/ It is totally unacceptable that you don't do proper analysis of the patches you submit, and that you don't bother writing proper, readable changelogs. Your flippant "that is trivial and obvious" attitude towards changelogs is unacceptable as well. And this is not about English knowledge: missing capitalization is a very simple concept any beginning coder should be able to graps the first time it's pointed out... yet for the past 3 years half of your patches had totally careless, often unreadable changelogs. These subpar changelogs and patches show plain laziness, sloppiness and lack of care to write clean changelogs - and that sloppiness not only makes it much harder for maintainers to process your patches, but also tends to creep over into your patches as well, causing repeat problems again and again... Thanks, Ingo
WARNING: multiple messages have this Message-ID (diff)
From: Ingo Molnar <mingo-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org> To: Yinghai Lu <yinghai-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org> Cc: Borislav Petkov <bp-Gina5bIWoIWzQB+pC5nmwQ@public.gmane.org>, Matt Fleming <matt.fleming-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>, "H. Peter Anvin" <hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>, Bjorn Helgaas <bhelgaas-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>, Thomas Gleixner <tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>, Ingo Molnar <mingo-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>, Jiri Kosina <jkosina-AlSwsSmVLrQ@public.gmane.org>, Borislav Petkov <bp-l3A5Bk7waGM@public.gmane.org>, Baoquan He <bhe-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>, Linux Kernel Mailing List <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>, "linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" <linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>, "linux-pci-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" <linux-pci-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>, Kees Cook <keescook-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org> Subject: Re: [PATCH v2 04/15] x86, kaslr: get kaslr_enabled back correctly Date: Wed, 4 Mar 2015 21:00:00 +0100 [thread overview] Message-ID: <20150304200000.GB6276@gmail.com> (raw) In-Reply-To: <CAE9FiQWKNDgzJtDVV34e7vWTu7LtqdDKB4KiN1RZwcZrX70zSA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> * Yinghai Lu <yinghai-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org> wrote: > On Wed, Mar 4, 2015 at 2:16 AM, Borislav Petkov <bp-Gina5bIWoIWzQB+pC5nmwQ@public.gmane.org> wrote: > > On Wed, Mar 04, 2015 at 12:00:37AM -0800, Yinghai Lu wrote: > >> commit f47233c2d34f ("x86/mm/ASLR: Propagate base load address calculation") > >> is using address as value for kaslr_enabled. > >> > >> That will random kaslr_enabled get that set or cleared. > >> Will have problem for system really have kaslr enabled. > >> > >> -v2: update changelog. > > > > This is still not good enough. Please do this: > > > > In commit f47233c2d34f we did A. The problem with that is B. Change the > > code to do C. > > > > Now you only have to fill out the A,B and C variables with the > > respective text which is understandable even for people who don't know > > this code. > > > > I don't know, that is trivial and obvious. The fix might be obvious, the effects of the bug are not obvious at all, as you yourself show that you don't understand your own change, which is evident from the changelog you've written: > Please check if it is ok: > > Subject: [PATCH v3] x86, kaslr: get kaslr_enabled back correctly Missing capitalization. > > commit f47233c2d34f ("x86/mm/ASLR: Propagate base load address calculation") > is using address as value for kaslr_enabled. Missing capitalization. Do you really expect maintainers to fix up every single sentence of yours?? > That will get wrong value for kaslr_enabled, so have problem for > system really have kaslr enabled. This sentence does not parse, nor is it correct: the bug isn't just triggering on systems that want to have kaslr enabled - but also on bootloaders that happen to pass in a kaslr boot parameter but have the switch value disabled... You also need to point out the important fact that bootloaders that don't try to use the kaslr extension (i.e. that don't use SETUP_KASLR) work just fine - this is why the bug was not noticed to begin with, i.e. the overwhelming majority of systems out there. > This patch change to using early map and accessing the value. s/change to using/changes the code to use/ It is totally unacceptable that you don't do proper analysis of the patches you submit, and that you don't bother writing proper, readable changelogs. Your flippant "that is trivial and obvious" attitude towards changelogs is unacceptable as well. And this is not about English knowledge: missing capitalization is a very simple concept any beginning coder should be able to graps the first time it's pointed out... yet for the past 3 years half of your patches had totally careless, often unreadable changelogs. These subpar changelogs and patches show plain laziness, sloppiness and lack of care to write clean changelogs - and that sloppiness not only makes it much harder for maintainers to process your patches, but also tends to creep over into your patches as well, causing repeat problems again and again... Thanks, Ingo
next prev parent reply other threads:[~2015-03-04 20:00 UTC|newest] Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-03-04 8:00 [PATCH v2 00/15] x86, boot: clean up kasl and setup_data handling Yinghai Lu 2015-03-04 8:00 ` [PATCH v2 01/15] x86, kaslr: Use init_size instead of run_size Yinghai Lu 2015-03-06 13:55 ` Borislav Petkov 2015-03-06 18:44 ` Yinghai Lu 2015-03-06 18:55 ` Kees Cook 2015-03-06 18:55 ` Kees Cook 2015-03-06 19:28 ` Yinghai Lu 2015-03-06 19:56 ` Kees Cook 2015-03-06 19:56 ` Kees Cook 2015-03-07 0:52 ` Yinghai Lu 2015-03-07 0:52 ` Yinghai Lu 2015-03-04 8:00 ` [PATCH v2 02/15] x86, boot: move ZO to end of buffer Yinghai Lu 2015-03-06 13:58 ` Borislav Petkov 2015-03-04 8:00 ` [PATCH v2 03/15] x86, boot: keep data from ZO boot stage to VO kernel stage Yinghai Lu 2015-03-04 8:00 ` [PATCH v2 04/15] x86, kaslr: get kaslr_enabled back correctly Yinghai Lu 2015-03-04 8:00 ` Yinghai Lu 2015-03-04 10:16 ` Borislav Petkov 2015-03-04 15:54 ` Jiri Kosina 2015-03-04 18:12 ` Yinghai Lu 2015-03-04 18:12 ` Yinghai Lu 2015-03-04 19:41 ` Ingo Molnar 2015-03-04 19:41 ` Ingo Molnar 2015-03-05 2:58 ` joeyli 2015-03-05 3:20 ` Yinghai Lu 2015-03-04 18:06 ` Yinghai Lu 2015-03-04 18:56 ` Yinghai Lu 2015-03-04 20:00 ` Ingo Molnar [this message] 2015-03-04 20:00 ` Ingo Molnar 2015-03-04 21:32 ` Yinghai Lu 2015-03-06 13:33 ` Borislav Petkov 2015-03-06 17:49 ` Yinghai Lu 2015-03-06 17:49 ` Yinghai Lu 2015-03-07 20:50 ` Borislav Petkov 2015-03-06 19:50 ` Yinghai Lu 2015-03-06 19:50 ` Yinghai Lu 2015-03-06 19:53 ` Yinghai Lu 2015-03-06 19:53 ` Yinghai Lu 2015-03-07 21:05 ` Borislav Petkov 2015-03-07 21:11 ` Yinghai Lu 2015-03-07 20:56 ` Borislav Petkov 2015-03-04 8:00 ` [PATCH v2 05/15] x86, kaslr: consolidate the mem_avoid filling Yinghai Lu 2015-03-04 8:00 ` Yinghai Lu 2015-03-04 8:00 ` [PATCH v2 06/15] x86, boot: split kernel_ident_mapping_init into another file Yinghai Lu 2015-03-04 8:00 ` [PATCH v2 07/15] x86, kaslr, 64bit: set new or extra ident_mapping Yinghai Lu 2015-03-04 8:00 ` [PATCH v2 08/15] x86: Kill E820_RESERVED_KERN Yinghai Lu 2015-03-04 8:00 ` Yinghai Lu 2015-03-04 8:00 ` [PATCH v2 09/15] x86, efi: copy SETUP_EFI data and access directly Yinghai Lu 2015-03-04 8:00 ` Yinghai Lu 2015-03-04 8:00 ` [PATCH v2 10/15] x86, of: let add_dtb reserve by itself Yinghai Lu 2015-03-04 8:00 ` [PATCH v2 11/15] x86, boot: Add add_pci handler for SETUP_PCI Yinghai Lu 2015-03-04 8:00 ` [PATCH v2 12/15] x86: kill not used setup_data handling code Yinghai Lu 2015-03-04 8:00 ` Yinghai Lu 2015-03-04 8:00 ` [PATCH v2 13/15] x86, pci: convert SETUP_PCI data to list Yinghai Lu 2015-03-04 8:00 ` [PATCH v2 14/15] x86, boot: copy rom to kernel space Yinghai Lu 2015-03-04 8:00 ` [PATCH v2 15/15] x86, pci: export SETUP_PCI data via sysfs Yinghai Lu
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20150304200000.GB6276@gmail.com \ --to=mingo@kernel.org \ --cc=bhe@redhat.com \ --cc=bhelgaas@google.com \ --cc=bp@alien8.de \ --cc=bp@suse.de \ --cc=hpa@zytor.com \ --cc=jkosina@suse.cz \ --cc=keescook@chromium.org \ --cc=linux-efi@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-pci@vger.kernel.org \ --cc=matt.fleming@intel.com \ --cc=mingo@redhat.com \ --cc=tglx@linutronix.de \ --cc=yinghai@kernel.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.