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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c344e6bd-1a95-4982-927d-f679410c444b@opensource.cirrus.com>
Date: Tue, 15 Apr 2025 13:03:18 +0100
From: Richard Fitzgerald <rf@...nsource.cirrus.com>
To: Thorsten Blum <thorsten.blum@...ux.dev>, Mark Brown <broonie@...nel.org>
Cc: David Rhodes <david.rhodes@...rus.com>, Jaroslav Kysela <perex@...ex.cz>,
        Takashi Iwai <tiwai@...e.com>, Kees Cook <kees@...nel.org>,
        "Gustavo A. R. Silva" <gustavoars@...nel.org>,
        linux-sound@...r.kernel.org, patches@...nsource.cirrus.com,
        linux-kernel@...r.kernel.org, linux-hardening@...r.kernel.org
Subject: Re: [PATCH] ASoC: cs-amp-lib: Annotate struct cirrus_amp_efi_data
 with __counted_by()

On 15/04/2025 12:51 pm, Thorsten Blum wrote:
> On 15. Apr 2025, at 12:56, Mark Brown wrote:
>> On Tue, Apr 15, 2025 at 11:03:55AM +0200, Thorsten Blum wrote:
>>> Add the __counted_by() compiler attribute to the flexible array member
>>> 'data' to improve access bounds-checking via CONFIG_UBSAN_BOUNDS and
>>> CONFIG_FORTIFY_SOURCE.
>>
>> As documented in submitting-patches.rst please send patches to the
>> maintainers for the code you would like to change.  The normal kernel
>> workflow is that people apply patches from their inboxes, if they aren't
>> copied they are likely to not see the patch at all and it is much more
>> difficult to apply patches.
> 
> I just use whatever scripts/get_maintainer.pl outputs. Maybe the
> MAINTAINERS file should be updated?
> 
> Best,
> Thorsten
> 

MAINTAINERS only lists Takashi and Jaroslav as maintainers of
include/sound/*.

A separate section lists Mark as maintainer of a specific set of files
within include/sound/

I guess any files we put in include/sound that are for an ASoC driver
have to also be added to Mark's ASoC section of MAINTAINERS?

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ