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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 19 May 2022 23:30:02 -0700 From: Eric Biggers <ebiggers@...nel.org> To: "Darrick J. Wong" <djwong@...nel.org> Cc: linux-fsdevel@...r.kernel.org, linux-ext4@...r.kernel.org, linux-f2fs-devel@...ts.sourceforge.net, linux-xfs@...r.kernel.org, linux-api@...r.kernel.org, linux-fscrypt@...r.kernel.org, linux-block@...r.kernel.org, linux-kernel@...r.kernel.org, Keith Busch <kbusch@...nel.org> Subject: Re: [RFC PATCH v2 1/7] statx: add I/O alignment information On Thu, May 19, 2022 at 04:06:05PM -0700, Darrick J. Wong wrote: > I guess that means for XFS it's effectively max(pagesize, i_blocksize, > bdev io_opt, sb_width, and (pretend XFS can reflink the realtime volume) > the rt extent size)? I didn't see a manpage update for statx(2) but > that's mostly what I'm interested in. :) I'll send out a man page update with the next version. I don't think there will be much new information that isn't already included in this patchset, though. > Looking ahead, it looks like the ext4/f2fs implementations only seem to > be returning max(i_blocksize, bdev io_opt)? But not the pagesize? I think that's just an oversight. ext4 and f2fs should round the value up to PAGE_SIZE. - Eric
Powered by blists - more mailing lists