On Wed, 2 Apr 2025 at 13:13, Jaco Kroon <jaco@xxxxxxxxx> 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
