From: Steve French <smfrench@gmail.com>
To: CIFS <linux-cifs@vger.kernel.org>, David Howells <dhowells@redhat.com>
Cc: Christian Brauner <brauner@kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: cifs
Date: Sat, 11 May 2024 12:53:34 -0500 [thread overview]
Message-ID: <CAH2r5mvvRFnzYnOM5T7qP+7H2Jetcv4cePhBPRDkd0ZwOGJfvg@mail.gmail.com> (raw)
Tried running the regression tests against for-next and saw crash
early in the test run in
# FS QA Test No. cifs/006
#
# check deferred closes on handles of deleted files
#
umount: /mnt/test: not mounted.
umount: /mnt/test: not mounted.
umount: /mnt/scratch: not mounted.
umount: /mnt/scratch: not mounted.
./run-xfstests.sh: line 25: 4556 Segmentation fault rmmod cifs
modprobe: ERROR: could not insert 'cifs': Device or resource busy
More information here:
http://smb311-linux-testing.southcentralus.cloudapp.azure.com/#/builders/5/builds/123/steps/14/logs/stdio
Are you also seeing that? There are not many likely candidates for
what patch is causing the problem (could be related to the folios
changes) e.g.
7c1ac89480e8 cifs: Enable large folio support
3ee1a1fc3981 cifs: Cut over to using netfslib
69c3c023af25 cifs: Implement netfslib hooks
c20c0d7325ab cifs: Make add_credits_and_wake_if() clear deducted credits
edea94a69730 cifs: Add mempools for cifs_io_request and
cifs_io_subrequest structs
3758c485f6c9 cifs: Set zero_point in the copy_file_range() and
remap_file_range()
1a5b4edd97ce cifs: Move cifs_loose_read_iter() and
cifs_file_write_iter() to file.c
dc5939de82f1 cifs: Replace the writedata replay bool with a netfs sreq flag
56257334e8e0 cifs: Make wait_mtu_credits take size_t args
ab58fbdeebc7 cifs: Use more fields from netfs_io_subrequest
a975a2f22cdc cifs: Replace cifs_writedata with a wrapper around
netfs_io_subrequest
753b67eb630d cifs: Replace cifs_readdata with a wrapper around
netfs_io_subrequest
0f7c0f3f5150 cifs: Use alternative invalidation to using launder_folio
2e9d7e4b984a mm: Remove the PG_fscache alias for PG_private_2
Any ideas?
--
Thanks,
Steve
next reply other threads:[~2024-05-11 17:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-11 17:53 Steve French [this message]
2024-05-11 17:59 ` cifs Steve French
2024-05-13 7:34 ` cifs Steve French
2024-05-13 21:24 ` cifs Steve French
-- strict thread matches above, loose matches on Subject: below --
2012-10-12 18:50 cifs Jeff Layton
[not found] ` <20121012145002.0e4b425a-4QP7MXygkU+dMjc06nkz3ljfA9RmPOcC@public.gmane.org>
2012-10-14 3:08 ` cifs Shirish Pargaonkar
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=CAH2r5mvvRFnzYnOM5T7qP+7H2Jetcv4cePhBPRDkd0ZwOGJfvg@mail.gmail.com \
--to=smfrench@gmail.com \
--cc=brauner@kernel.org \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).