linux-kernel - Re: [PATCH 2/2] fuse: Adjust readdir() buffer to requesting buffer size.

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: <CAJfpegsx=_wbBtVG1wQj6ZWzEfwknJvqfLXnDONPrdUwJRVPEg@mail.gmail.com>
Date: Wed, 2 Apr 2025 13:35:16 +0200
From: Miklos Szeredi <miklos@...redi.hu>
To: Jaco Kroon <jaco@....co.za>
Cc: Bernd Schubert <bernd.schubert@...tmail.fm>, linux-fsdevel@...r.kernel.org, 
	linux-kernel@...r.kernel.org, christophe.jaillet@...adoo.fr, 
	joannelkoong@...il.com, rdunlap@...radead.org, trapexit@...wn.link, 
	david.laight.linux@...il.com
Subject: Re: [PATCH 2/2] fuse: Adjust readdir() buffer to requesting buffer size.

On Wed, 2 Apr 2025 at 13:13, Jaco Kroon <jaco@....co.za> wrote:

> How do I go about confirming?  Can that behaviour be stopped so that in
> the case where it would block we can return an EAGAIN or EWOULDBLOCK
> error code instead?  Is that even desired?

All allocations except GFP_ATOMIC may block (that applies to
folio_alloc() and kmalloc() too).  This shouldn't be a worry in the
readdir path.  Freeing can safely be done in an atomic context.

Thanks,
Miklos