From: Paulo Alcantara <pc@manguebit.org>
To: Siddharth Chintamaneni <sidchintamaneni@gmail.com>,
Sasha Levin <sashal@kernel.org>
Cc: stable@vger.kernel.org, gregkh@linuxfoundation.org,
wozizhi@huawei.com, lsahlber@redhat.com, sprasad@microsoft.com,
tom@talpey.com, glaming@microsoft.com,
linux-cifs@vger.kernel.org, apais@microsoft.com,
rlmenge@gmail.com, hargar@linux.microsoft.com
Subject: Re: [PATCH 6.6.y] smb: client: fix busy dentry warning on unmount after DIO
Date: Tue, 03 Nov 2026 19:30:19 -0300 [thread overview]
Message-ID: <7bd9007e90f271821114f617fda2c1ee@manguebit.org> (raw)
In-Reply-To: <CAE5sdEi4GOXeVDPEUk-RR7bjE8z=25f+waQNedMQd6VCum3TrQ@mail.gmail.com>
Siddharth Chintamaneni <sidchintamaneni@gmail.com> writes:
> On Tue, 3 Nov 2026 at 06:52, Sasha Levin <sashal@kernel.org> wrote:
>>
>> > commit 75f5c412fa867efa0bf9b646bffe0d912109e84a upstream.
>> >
>> > Kernel 6.6 predates the netfs I/O request conversion and instead splits
>> > I/O across three reference-counted structures that each hold a
>> > cifsFileInfo reference
>>
>> This is a hand-written 6.6 adaptation of 75f5c412fa86 ("smb: client: fix busy
>> dentry warning on unmount after DIO") rather than a cherry-pick, so I need an
>> ack from a cifs maintainer (Steve French or Paulo Alcantara) on the list before
>> queueing it. 6.1 also has 340cea84f691 and the same bug; please send a 6.1
>> variant too.
>>
>
> CC'ing Paulo Alcantara's correct email for review. Thanks!
LGTM.
Acked-by: Paulo Alcantara <pc@manguebit.org>
next prev parent reply other threads:[~2026-11-03 22:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-02 20:14 [PATCH 6.6.y] smb: client: fix busy dentry warning on unmount after DIO Siddharth Chintamaneni
2026-11-03 14:51 ` Sasha Levin
2026-11-03 21:41 ` Siddharth Chintamaneni
2026-11-03 22:30 ` Paulo Alcantara [this message]
2026-11-03 22:48 ` Siddharth Chintamaneni
2026-11-04 15:03 ` Sasha Levin
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=7bd9007e90f271821114f617fda2c1ee@manguebit.org \
--to=pc@manguebit.org \
--cc=apais@microsoft.com \
--cc=glaming@microsoft.com \
--cc=gregkh@linuxfoundation.org \
--cc=hargar@linux.microsoft.com \
--cc=linux-cifs@vger.kernel.org \
--cc=lsahlber@redhat.com \
--cc=rlmenge@gmail.com \
--cc=sashal@kernel.org \
--cc=sidchintamaneni@gmail.com \
--cc=sprasad@microsoft.com \
--cc=stable@vger.kernel.org \
--cc=tom@talpey.com \
--cc=wozizhi@huawei.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