From: Paulo Alcantara <pc@manguebit.org>
To: Siddharth Chintamaneni <sidchintamaneni@gmail.com>
Cc: Ronnie Sahlberg <ronniesahlberg@gmail.com>,
Shyam Prasad N <sprasad@microsoft.com>,
Tom Talpey <tom@talpey.com>, Bharath SM <bharathsm@microsoft.com>,
Allen Pais <apais@microsoft.com>,
Rachel Menge <rachelmenge@linux.microsoft.com>,
Hardik Garg <hargar@linux.microsoft.com>,
Adam Kim <adamkim@microsoft.com>,
Siddharth Chintamaneni <sidchintamaneni@gmail.com>,
linux-cifs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 0/2] smb: client: fix unmount busy dentry/inode races on openFileList
Date: Thu, 19 Nov 2026 10:46:58 -0300 [thread overview]
Message-ID: <8f92dc00f05e67e7fe0dc35a4263299c@manguebit.org> (raw)
In-Reply-To: <20261117001733.192399-1-sidchintamaneni@gmail.com>
Siddharth Chintamaneni <sidchintamaneni@gmail.com> writes:
> This series fixes two unmount races in cifs_kill_sb() where background
> paths walk tcon->openFileList while wait_var_event() is waiting on
> cifs_sb->outstanding_rreq and take new cifsFileInfo references that
> outlive the wait, causing busy dentry/inode warnings and panics in
> generic_shutdown_super():
>
> - Patch 1 counts queued oplock/lease breaks in cifs_sb->outstanding_rreq
> from cifs_queue_oplock_break() until cifs_oplock_break() completes.
> - Patch 2 counts persistent handle reopens in cifs_sb->outstanding_rreq
> in cifs_reopen_persistent_handles() until cifsFileInfo_put() drops the
> handle reference.
> ...
Applied.
prev parent reply other threads:[~2026-11-19 13:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-17 0:17 Siddharth Chintamaneni
2026-11-17 0:17 ` [PATCH v1 1/2] smb: client: fix busy dentry and inode on unmount from late oplock break Siddharth Chintamaneni
2026-11-17 0:17 ` [PATCH v1 2/2] smb: client: fix busy dentry on unmount from persistent handle reopen Siddharth Chintamaneni
2026-11-19 13:46 ` Paulo Alcantara [this message]
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=8f92dc00f05e67e7fe0dc35a4263299c@manguebit.org \
--to=pc@manguebit.org \
--cc=adamkim@microsoft.com \
--cc=apais@microsoft.com \
--cc=bharathsm@microsoft.com \
--cc=hargar@linux.microsoft.com \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rachelmenge@linux.microsoft.com \
--cc=ronniesahlberg@gmail.com \
--cc=sidchintamaneni@gmail.com \
--cc=sprasad@microsoft.com \
--cc=tom@talpey.com \
/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
all inboxes | Powered by JetHome®