Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1622637

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

From Kees Cook <keescook@chromium.org>
Newsgroups linux.kernel
Subject Re: [PATCH v2] scsi/bfa: use designated initializers
Date 2017-04-13 02:30 +0200
Message-ID <tvAO5-3w4-5@gated-at.bofh.it> (permalink)
References <tqsRc-3S4-19@gated-at.bofh.it> <tqDth-3qZ-27@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On Thu, Mar 30, 2017 at 1:18 AM, Christoph Hellwig <hch@lst.de> wrote:
> On Wed, Mar 29, 2017 at 01:55:09PM -0700, 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 grsecurity.
>>
>> Signed-off-by: Kees Cook <keescook@chromium.org>
>> ---
>> This has been updated now that struct bfa_fcs_mod_s was dropped.
>
> Can you also add designated array initializers for __port_action while
> you're at it?

Hrm? This is what the patch already does. It adds them for both
__port_action and struct bfa_module_s.

-Kees

-- 
Kees Cook
Pixel Security

Back to linux.kernel | Previous | NextNext in thread | Find similar | Unroll thread


Thread

Re: [PATCH v2] scsi/bfa: use designated initializers Kees Cook <keescook@chromium.org> - 2017-04-13 02:30 +0200
  Re: [PATCH v2] scsi/bfa: use designated initializers Christoph Hellwig <hch@lst.de> - 2017-04-13 09:10 +0200

csiph-web