linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steve French <smfrench@gmail.com>
To: CIFS <linux-cifs@vger.kernel.org>, David Howells <dhowells@redhat.com>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: netfs read failures with current mainline
Date: Mon, 17 Feb 2025 15:01:08 -0600	[thread overview]
Message-ID: <CAH2r5mvgkPdLQ_oz_faa=4CVCaHNDcNVZfqBbdKTENrW5COSTA@mail.gmail.com> (raw)

I see many "Couldn't get user pages" netfs errors running cifs/102
regression test (which tests for leaked file handles) when using
current mainline from today (which includes the recent netfs read
retry fixes).  For example many of:

[Mon Feb 17 14:08:31 2025] netfs: Couldn't get user pages (rc=-4)
[Mon Feb 17 14:08:31 2025] netfs: Zero-sized read [R=32f]
[Mon Feb 17 14:08:31 2025] netfs: Couldn't get user pages (rc=-4)

Anyone else see netfs problems when running with current mainline?

The test does the following (checking for handle leaks):

# Create a file to test with
echo "hello world" > $TEST_DIR/leak
# Try to kill a 'cat' when it is opening/closing a file
(for i in {1..5000} ; do cat $TEST_DIR/leak & sleep 0.0001 ; kill -9
$! ; done) >/dev/null 2>&1
sleep 3
# and verify if we have any leaked filehandles
smbstatus | grep -i Locked -A1000

-- 
Thanks,

Steve

             reply	other threads:[~2025-02-17 21:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-17 21:01 Steve French [this message]
2025-02-19 16:26 ` netfs read failures with current mainline David Howells
2025-02-20  6:01   ` Steve French
2025-02-19 16:45 ` David Howells

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAH2r5mvgkPdLQ_oz_faa=4CVCaHNDcNVZfqBbdKTENrW5COSTA@mail.gmail.com' \
    --to=smfrench@gmail.com \
    --cc=dhowells@redhat.com \
    --cc=linux-cifs@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).