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: <Y4j142NC7u0O8VHt@sol.localdomain> Date: Thu, 1 Dec 2022 10:43:47 -0800 From: Eric Biggers <ebiggers@...nel.org> To: Jan Kara <jack@...e.cz> Cc: "yebin (H)" <yebin10@...wei.com>, Ye Bin <yebin@...weicloud.com>, tytso@....edu, adilger.kernel@...ger.ca, linux-ext4@...r.kernel.org, linux-kernel@...r.kernel.org, syzbot+4d99a966fd74bdeeec36@...kaller.appspotmail.com Subject: Re: [PATCH] ext4: fix WARNING in ext4_expand_extra_isize_ea On Thu, Dec 01, 2022 at 03:21:43PM +0100, Jan Kara wrote: > You're right that VFS actually limits xattr size to 64k. So the chances > that someone actually has filesystem with larger xattrs are slim. But I > know that Lustre guys run with their modified kernels and they were the > ones implementing ea_inode feature so maybe they'd bumped the VFS limit as > well in their kernels. Upstream has 64K, so that's all that matters in the context of upstream. If someone changed it downstream, that's their problem. - Eric
Powered by blists - more mailing lists