linux-kernel - [PATCH 0/2 v2] Move all file-close work for nfsd into nfsd threads

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20231204014042.6754-1-neilb@suse.de>
Date:   Mon,  4 Dec 2023 12:36:40 +1100
From:   NeilBrown <neilb@...e.de>
To:     Al Viro <viro@...iv.linux.org.uk>,
        Christian Brauner <brauner@...nel.org>,
        Jens Axboe <axboe@...nel.dk>, Oleg Nesterov <oleg@...hat.com>,
        Chuck Lever <chuck.lever@...cle.com>,
        Jeff Layton <jlayton@...nel.org>,
        Ingo Molnar <mingo@...hat.com>,
        Peter Zijlstra <peterz@...radead.org>,
        Juri Lelli <juri.lelli@...hat.com>,
        Vincent Guittot <vincent.guittot@...aro.org>
Cc:     linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
        linux-nfs@...r.kernel.org
Subject: [PATCH 0/2 v2] Move all file-close work for nfsd into nfsd threads

Hi,
  here is a revised version of my previous patch titled:
   [PATCH/RFC] core/nfsd: allow kernel threads to use task_work.

  There are now two patches - one that changes core code to allow nfsd
  to handle its own __dput calls, and one to make various changes to
  nfsd.

  It would probably make sense for the first patch to land through the
  VFS tree, and the second to follow through the NFSD tree, maybe after the relevant rc1 ??

  Details of the problem and explanation of the solution are in the individual patches.
  Thanks for all the review and suggestions.

NeilBrown

 [PATCH 1/2] Allow a kthread to declare that it calls task_work_run()
 [PATCH 2/2] nfsd: Don't leave work of closing files to a work queue.