[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJZ5v0hqRbsivmnG5iKMsR_ZMg+i_vxA7n-NOkuu3jh-TJ6pHw@mail.gmail.com>
Date: Tue, 20 Jun 2017 23:34:38 +0200
From: "Rafael J. Wysocki" <rafael@...nel.org>
To: Christoph Hellwig <hch@...radead.org>
Cc: Kees Cook <keescook@...omium.org>,
"kernel-hardening@...ts.openwall.com" <kernel-hardening@...ts.openwall.com>, LKML <linux-kernel@...r.kernel.org>,
"Rafael J. Wysocki" <rjw@...ysocki.net>, Len Brown <lenb@...nel.org>,
ACPI Devel Maling List <linux-acpi@...r.kernel.org>, Linus Torvalds <torvalds@...ux-foundation.org>,
Robert Moore <robert.moore@...el.com>, Lv Zheng <lv.zheng@...el.com>
Subject: Re: [PATCH 3/4] randstruct: Disable randomization of ACPICA structs
On Tue, Jun 20, 2017 at 10:35 PM, Christoph Hellwig <hch@...radead.org> wrote:
> On Tue, Jun 20, 2017 at 12:25:53PM -0700, Kees Cook wrote:
>> Can you send the patch to https://github.com/acpica/acpica ? My change
>> was finally accepted, so this whole issue will go away on the next
>> refresh. Until then, I don't want to block the entire automatic
>> structure selection logic of randstruct on a three-function table. :)
>
> I do not have a github account and no such thing is required for kernel
> development.
It isn't required for the ACPICA material either.
You just need to CC the ACPICA maintainers, as per MAINTAINERS, on
your ACPICA patches. They pick up stuff that looks good to them.
And we tend to prefer routing ACPICA changes through the upstream,
because failing to do so usually turns out to be painful in the long
term. I don't think it is unreasonable to ask for cooperation in that
respect.
Thanks,
Rafael
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
