linux-hardening - Re: [PATCH][next] scsi: mptlan: Replace one-element array with flexible-array member

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <b1354342-e9c9-5fea-ab50-e996fb790a5f@embeddedor.com>
Date:   Tue, 6 Apr 2021 04:58:21 -0500
From:   "Gustavo A. R. Silva" <gustavo@...eddedor.com>
To:     "Martin K. Petersen" <martin.petersen@...cle.com>,
        "Gustavo A. R. Silva" <gustavoars@...nel.org>,
        Suganath Prabu Subramani 
        <suganath-prabu.subramani@...adcom.com>,
        Sreekanth Reddy <sreekanth.reddy@...adcom.com>,
        Sathya Prakash <sathya.prakash@...adcom.com>
Cc:     linux-scsi@...r.kernel.org, linux-kernel@...r.kernel.org,
        linux-hardening@...r.kernel.org, MPT-FusionLinux.pdl@...adcom.com
Subject: Re: [PATCH][next] scsi: mptlan: Replace one-element array with
 flexible-array member

Hi Martin,

On 4/5/21 23:53, Martin K. Petersen wrote:
> On Wed, 24 Mar 2021 18:33:44 -0500, Gustavo A. R. Silva wrote:
> 
>> There is a regular need in the kernel to provide a way to declare having
>> a dynamically sized set of trailing elements in a structure. Kernel code
>> should always use “flexible array members”[1] for these cases. The older
>> style of one-element or zero-length arrays should no longer be used[2].
>>
>> Refactor the code according to the use of a flexible-array member in
>> struct _SGE_TRANSACTION32 instead of one-element array.
>>
>> [...]
> 
> Applied to 5.13/scsi-queue, thanks!
> 
> [1/1] scsi: mptlan: Replace one-element array with flexible-array member
>       https://git.kernel.org/mkp/scsi/c/4e2e619f3c9e
> 

Thanks for this.

Could you apply this one, too:
https://lore.kernel.org/lkml/20210304203822.GA102218@embeddedor/

This was my last reply to the thread:
https://lore.kernel.org/lkml/d79bde59-16c5-e006-0e31-c33c17f0ce3d@embeddedor.com/

Thanks!
--
Gustavo