Re: [PATCH] scsi/bfa: use designated initializers

2017-01-08 Thread Christoph Hellwig
On Tue, Jan 03, 2017 at 03:25:22PM -0800, Kees Cook wrote: > Sounds fine to me! Is this going via your tree? I don't have a suitable tree, but I'll resend it to the scsi list in a separate thread ASAP. -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a

Re: [PATCH] scsi/bfa: use designated initializers

2017-01-03 Thread Kees Cook
On Wed, Dec 21, 2016 at 12:33 AM, Christoph Hellwig wrote: > On Fri, Dec 16, 2016 at 05:05:15PM -0800, Kees Cook wrote: >> Prepare to mark sensitive kernel structures for randomization by making >> sure they're using designated initializers. These were identified during >>

Re: [PATCH] scsi/bfa: use designated initializers

2016-12-21 Thread Christoph Hellwig
On Fri, Dec 16, 2016 at 05:05:15PM -0800, Kees Cook wrote: > Prepare to mark sensitive kernel structures for randomization by making > sure they're using designated initializers. These were identified during > allyesconfig builds of x86, arm, and arm64, with most initializer fixes > extracted from

[PATCH] scsi/bfa: use designated initializers

2016-12-16 Thread Kees Cook
Prepare to mark sensitive kernel structures for randomization by making sure they're using designated initializers. These were identified during allyesconfig builds of x86, arm, and arm64, with most initializer fixes extracted from grsecurity. Signed-off-by: Kees Cook ---