From: Chao Fan <fanc.fnst@cn.fujitsu.com> To: Baoquan He <bhe@redhat.com> Cc: Masayoshi Mizuma <msys.mizuma@gmail.com>, Borislav Petkov <bp@alien8.de>, Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@kernel.org>, linux-kernel@vger.kernel.org, x86@kernel.org, linux-efi@vger.kernel.org, linux-acpi@vger.kernel.org, mingo@redhat.com, hpa@zytor.com, keescook@chromium.org, rjw@rjwysocki.net, lenb@kernel.org, ard.biesheuvel@linaro.org, indou.takao@jp.fujitsu.com, caoj.fnst@cn.fujitsu.com Subject: Re: [PATCH v8 0/3] x86/boot/KASLR: Parse ACPI table and limit kaslr in immovable memory Date: Thu, 11 Oct 2018 13:51:54 +0800 [thread overview] Message-ID: <20181011055154.GB6667@localhost.localdomain> (raw) In-Reply-To: <20181011002955.GJ25297@MiWiFi-R3L-srv> On Thu, Oct 11, 2018 at 08:29:55AM +0800, Baoquan He wrote: >On 10/10/18 at 03:44pm, Masayoshi Mizuma wrote: >> On Wed, Oct 10, 2018 at 05:30:57PM +0800, Baoquan He wrote: >> > On 10/10/18 at 11:19am, Borislav Petkov wrote: >> > > On Wed, Oct 10, 2018 at 11:14:26AM +0200, Thomas Gleixner wrote: >> > > > Yes, it's different, but if the SRAT information is available early, then >> > > > the command line parameter can go away because then the required >> > > > information for Masa's problem is available as well. >> > > >> > > Exactly. And I'd prefer we delayed the command line parameter until we >> > > figure out we really need it and not expose it to upstream and then >> > > remove it shortly after. >> > > >> > > So I'd suggest we move Masa's patches to a separate branch and not send >> > > it up this round. >> > >> > Yes, sounds more reasonable if we can reuse functions in Chao's patch 1/3 >> > to solve the padding issue. >> >> Thanks for your comments! Yes, immovable_mem[num_immovable_mem] in Chao's >> patch may be useful for calculating the padding size. If so, we don't >> need the new kernel parameter. It's nice! >> >> Do you happen to have ideas how we access immovable_mem[num_immovable_mem] >> from arch/x86/mm/kaslr.c ? It is located to arch/x86/boot/compressed/*, so >> I suppose it is not easy to access it... >> I would appreciate if you could give some advice. > >Hmm, they are living in different life cycle and space. So we can only >reuse the code from Chao's patch, but not the variable. Means we need >go through the SRAT accessing again in arch/x86/mm/kaslr.c and fill >immovable_mem[num_immovable_mem] for mm/kaslr.c usage, if we decide to >do like that. Reading three times is redundant, but reading two times is needed. Becasue the ACPI code run very stable, but we need more information before that. As for Masa's issue, I am wondering whether we can tranfer the information or only the address of SRAT table from compressed period to the period after start_kernel(). Thanks, Chao Fan > >Thanks >Baoquan > >
WARNING: multiple messages have this Message-ID (diff)
From: Chao Fan <fanc.fnst@cn.fujitsu.com> To: Baoquan He <bhe@redhat.com> Cc: Masayoshi Mizuma <msys.mizuma@gmail.com>, Borislav Petkov <bp@alien8.de>, Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@kernel.org>, <linux-kernel@vger.kernel.org>, <x86@kernel.org>, <linux-efi@vger.kernel.org>, <linux-acpi@vger.kernel.org>, <mingo@redhat.com>, <hpa@zytor.com>, <keescook@chromium.org>, <rjw@rjwysocki.net>, <lenb@kernel.org>, <ard.biesheuvel@linaro.org>, <indou.takao@jp.fujitsu.com>, <caoj.fnst@cn.fujitsu.com> Subject: Re: [PATCH v8 0/3] x86/boot/KASLR: Parse ACPI table and limit kaslr in immovable memory Date: Thu, 11 Oct 2018 13:51:54 +0800 [thread overview] Message-ID: <20181011055154.GB6667@localhost.localdomain> (raw) In-Reply-To: <20181011002955.GJ25297@MiWiFi-R3L-srv> On Thu, Oct 11, 2018 at 08:29:55AM +0800, Baoquan He wrote: >On 10/10/18 at 03:44pm, Masayoshi Mizuma wrote: >> On Wed, Oct 10, 2018 at 05:30:57PM +0800, Baoquan He wrote: >> > On 10/10/18 at 11:19am, Borislav Petkov wrote: >> > > On Wed, Oct 10, 2018 at 11:14:26AM +0200, Thomas Gleixner wrote: >> > > > Yes, it's different, but if the SRAT information is available early, then >> > > > the command line parameter can go away because then the required >> > > > information for Masa's problem is available as well. >> > > >> > > Exactly. And I'd prefer we delayed the command line parameter until we >> > > figure out we really need it and not expose it to upstream and then >> > > remove it shortly after. >> > > >> > > So I'd suggest we move Masa's patches to a separate branch and not send >> > > it up this round. >> > >> > Yes, sounds more reasonable if we can reuse functions in Chao's patch 1/3 >> > to solve the padding issue. >> >> Thanks for your comments! Yes, immovable_mem[num_immovable_mem] in Chao's >> patch may be useful for calculating the padding size. If so, we don't >> need the new kernel parameter. It's nice! >> >> Do you happen to have ideas how we access immovable_mem[num_immovable_mem] >> from arch/x86/mm/kaslr.c ? It is located to arch/x86/boot/compressed/*, so >> I suppose it is not easy to access it... >> I would appreciate if you could give some advice. > >Hmm, they are living in different life cycle and space. So we can only >reuse the code from Chao's patch, but not the variable. Means we need >go through the SRAT accessing again in arch/x86/mm/kaslr.c and fill >immovable_mem[num_immovable_mem] for mm/kaslr.c usage, if we decide to >do like that. Reading three times is redundant, but reading two times is needed. Becasue the ACPI code run very stable, but we need more information before that. As for Masa's issue, I am wondering whether we can tranfer the information or only the address of SRAT table from compressed period to the period after start_kernel(). Thanks, Chao Fan > >Thanks >Baoquan > >
next prev parent reply other threads:[~2018-10-11 5:51 UTC|newest] Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-10-10 8:41 [PATCH v8 0/3] x86/boot/KASLR: Parse ACPI table and limit kaslr in immovable memory Chao Fan 2018-10-10 8:41 ` Chao Fan 2018-10-10 8:41 ` [PATCH v8 1/3] x86/boot: Add acpitb.c to parse acpi tables Chao Fan 2018-10-10 8:41 ` Chao Fan 2018-10-11 10:57 ` Borislav Petkov 2018-10-12 1:56 ` Chao Fan 2018-10-12 1:56 ` Chao Fan 2018-10-12 9:36 ` Chao Fan 2018-10-12 9:36 ` Chao Fan 2018-10-12 9:46 ` Borislav Petkov 2018-10-12 10:03 ` Chao Fan 2018-10-12 10:03 ` Chao Fan 2018-10-16 2:48 ` Chao Fan 2018-10-16 2:48 ` Chao Fan 2018-10-16 12:40 ` Borislav Petkov 2018-10-17 1:10 ` Chao Fan 2018-10-17 1:10 ` Chao Fan 2018-10-15 20:26 ` Masayoshi Mizuma 2018-10-16 1:50 ` Chao Fan 2018-10-16 1:50 ` Chao Fan 2018-10-10 8:41 ` [PATCH v8 2/3] x86/boot/KASLR: Walk srat tables to filter immovable memory Chao Fan 2018-10-10 8:41 ` Chao Fan 2018-10-10 8:41 ` [PATCH v8 3/3] x86/boot/KASLR: Limit kaslr to choosing the " Chao Fan 2018-10-10 8:41 ` Chao Fan 2018-10-10 8:59 ` [PATCH v8 0/3] x86/boot/KASLR: Parse ACPI table and limit kaslr in " Borislav Petkov 2018-10-10 8:59 ` Borislav Petkov 2018-10-10 9:06 ` Baoquan He 2018-10-10 9:12 ` Chao Fan 2018-10-10 9:12 ` Chao Fan 2018-10-10 9:21 ` Baoquan He 2018-10-10 9:14 ` Thomas Gleixner 2018-10-10 9:19 ` Borislav Petkov 2018-10-10 9:30 ` Baoquan He 2018-10-10 19:44 ` Masayoshi Mizuma 2018-10-11 0:29 ` Baoquan He 2018-10-11 5:51 ` Chao Fan [this message] 2018-10-11 5:51 ` Chao Fan 2018-10-13 20:19 ` Masayoshi Mizuma 2018-10-13 20:34 ` Borislav Petkov 2018-10-13 21:45 ` Masayoshi Mizuma 2018-10-13 22:05 ` Borislav Petkov 2018-10-15 0:50 ` Masayoshi Mizuma 2018-10-16 15:13 ` Masayoshi Mizuma 2018-10-16 19:11 ` Borislav Petkov 2018-10-16 19:54 ` Masayoshi Mizuma 2018-10-16 19:59 ` Borislav Petkov 2018-10-22 15:42 ` Masayoshi Mizuma 2018-10-23 2:48 ` Chao Fan 2018-10-23 2:48 ` Chao Fan 2018-10-24 19:21 ` Masayoshi Mizuma 2018-10-25 1:22 ` Chao Fan 2018-10-25 1:22 ` Chao Fan 2018-10-25 10:33 ` Borislav Petkov 2018-10-25 13:40 ` Masayoshi Mizuma 2018-11-06 12:10 ` Borislav Petkov 2018-11-06 14:07 ` Baoquan He 2018-11-07 1:21 ` Chao Fan 2018-11-07 1:21 ` Chao Fan 2018-11-06 18:45 ` Borislav Petkov 2018-11-06 19:36 ` Masayoshi Mizuma 2018-11-06 20:45 ` Borislav Petkov 2018-11-06 22:21 ` Masayoshi Mizuma 2018-11-08 10:51 ` Borislav Petkov 2018-11-08 10:51 ` Borislav Petkov 2018-11-10 10:54 ` Borislav Petkov 2018-11-11 13:45 ` Masayoshi Mizuma 2019-02-05 15:05 ` Masayoshi Mizuma 2019-02-08 18:26 ` Borislav Petkov 2019-02-09 0:24 ` Masayoshi Mizuma 2019-02-11 1:46 ` Chao Fan 2019-02-11 1:46 ` Chao Fan 2019-02-11 20:11 ` Masayoshi Mizuma 2018-10-10 17:16 ` Borislav Petkov 2018-10-11 1:30 ` Chao Fan 2018-10-11 1:30 ` Chao Fan
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=20181011055154.GB6667@localhost.localdomain \ --to=fanc.fnst@cn.fujitsu.com \ --cc=ard.biesheuvel@linaro.org \ --cc=bhe@redhat.com \ --cc=bp@alien8.de \ --cc=caoj.fnst@cn.fujitsu.com \ --cc=hpa@zytor.com \ --cc=indou.takao@jp.fujitsu.com \ --cc=keescook@chromium.org \ --cc=lenb@kernel.org \ --cc=linux-acpi@vger.kernel.org \ --cc=linux-efi@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=mingo@kernel.org \ --cc=mingo@redhat.com \ --cc=msys.mizuma@gmail.com \ --cc=rjw@rjwysocki.net \ --cc=tglx@linutronix.de \ --cc=x86@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.