On Thu, Jan 20, 2022 at 12:27:45AM -0800, Christoph Hellwig wrote: > > +/** > > + * fscrypt_dio_unsupported() - check whether a DIO (direct I/O) request is > > + * unsupported due to encryption constraints > > + * @iocb: the file and position the I/O is targeting > > + * @iter: the I/O data segment(s) > > + * > > + * Return: true if DIO is unsupported > > + */ > > +bool fscrypt_dio_unsupported(struct kiocb *iocb, struct iov_iter *iter) > > I always find non-negated functions easier to follow, i.e. turn this > into fscrypt_dio_supported(). > I actually had changed this from v9 because fscrypt_dio_supported() seemed backwards, given that its purpose is to check whether DIO is unsupported, not whether it's supported per se (and the function's comment reflected this). What ext4 and f2fs do is check a list of reasons why DIO would *not* be supported, and if none apply, then it is supported. This is just one of those reasons. This is subjective though, so if people prefer the old way, I'll change it back. - Eric
