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
| ||
|
Message-ID: <173159220757.521904.13348650494002839092.b4-ty@mit.edu> Date: Thu, 14 Nov 2024 08:53:40 -0500 From: "Theodore Ts'o" <tytso@....edu> To: Andreas Dilger <adilger.kernel@...ger.ca>, Kees Cook <kees@...nel.org>, "Gustavo A. R. Silva" <gustavoars@...nel.org>, Thorsten Blum <thorsten.blum@...ux.dev> Cc: "Theodore Ts'o" <tytso@....edu>, Jan Kara <jack@...e.cz>, linux-ext4@...r.kernel.org, linux-kernel@...r.kernel.org, linux-hardening@...r.kernel.org Subject: Re: [PATCH v2] ext4: Annotate struct fname with __counted_by() On Tue, 05 Nov 2024 11:18:14 +0100, Thorsten Blum wrote: > Add the __counted_by compiler attribute to the flexible array member > name to improve access bounds-checking via CONFIG_UBSAN_BOUNDS and > CONFIG_FORTIFY_SOURCE. > > Applied, thanks! [1/1] ext4: Annotate struct fname with __counted_by() commit: de183b2baf90f0acc1854a3998c14b8b228f9643 By the way, in general, you don't need to resend patches unless you need to rebase them to fix patch conflicts; I track requested patches using patchwork, and I tend to process and review patches in batches. If you are concerned that I might have missed a patch, feel free to reply to the original patch with a ping. I'll see it in my inbox, and even if it had gotten lost in my inbox, I can find the original patch using lore.kernel.org or patchwork. Thanks! Best regards, -- Theodore Ts'o <tytso@....edu>
Powered by blists - more mailing lists