diff options
| author | Jeff Layton <jlayton@kernel.org> | 2025-02-20 11:47:15 -0500 |
|---|---|---|
| committer | Chuck Lever <chuck.lever@oracle.com> | 2025-03-10 09:11:10 -0400 |
| commit | 49bdbdb11f70edef73ff9015f9b4ce717338def9 (patch) | |
| tree | e1c0960597497b447d9d4cc386df03361dbe54c4 /tools/testing/selftests/bpf/prog_tests/autoload.c | |
| parent | 424dd3df1f991b14a70f044a68c8a595abbdf1ad (diff) | |
| download | linux-49bdbdb11f70edef73ff9015f9b4ce717338def9.tar.gz linux-49bdbdb11f70edef73ff9015f9b4ce717338def9.tar.bz2 linux-49bdbdb11f70edef73ff9015f9b4ce717338def9.zip | |
nfsd: replace CB_GETATTR_BUSY with NFSD4_CALLBACK_RUNNING
These flags serve essentially the same purpose and get set and cleared
at the same time. Drop CB_GETATTR_BUSY and just use
NFSD4_CALLBACK_RUNNING instead.
For this to work, we must use clear_and_wake_up_bit(), but doing that on
for other types of callbacks is wasteful. Declare a new NFSD4_CALLBACK_WAKE
flag in cb_flags to indicate that wake_up is needed, and only set that
for CB_GETATTRs.
Also, make the wait use a TASK_UNINTERRUPTIBLE sleep. This is done in
the context of an nfsd thread, and it should never need to deal with
signals.
Signed-off-by: Jeff Layton <jlayton@kernel.org>
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Diffstat (limited to 'tools/testing/selftests/bpf/prog_tests/autoload.c')
0 files changed, 0 insertions, 0 deletions