From: Kuniyuki Iwashima <kuniyu@amazon.com>
To: <smfrench@gmail.com>
Cc: <bharathsm@microsoft.com>, <ematsumiya@suse.de>,
<kuni1840@gmail.com>, <kuniyu@amazon.com>,
<linux-cifs@vger.kernel.org>, <pc@manguebit.com>,
<ronniesahlberg@gmail.com>, <samba-technical@lists.samba.org>,
<sfrench@samba.org>, <sprasad@microsoft.com>, <tom@talpey.com>,
<wangzhaolong1@huawei.com>
Subject: Re: [PATCH 1/2] Revert "smb: client: Fix netns refcount imbalance causing leaks and use-after-free"
Date: Thu, 3 Apr 2025 10:46:38 -0700 [thread overview]
Message-ID: <20250403174642.96094-1-kuniyu@amazon.com> (raw)
In-Reply-To: <CAH2r5mtvkAAEur6_jPMtvpKa8q9fWufwV7VG+fXkATXs_jZv0w@mail.gmail.com>
From: Steve French <smfrench@gmail.com>
Date: Thu, 3 Apr 2025 12:32:35 -0500
> > What branch should be used to send reverts for -rcX ?
>
> cifs-2.6.git for-next
>
> But probably won't be an issue in a few days (since mainline then will
> likely include the conflicting patch - which fortunately is unrelated
> to this discussion, just fixes an RFC1001 bug)
Thanks, then I'd leave v2 as is for now.
next prev parent reply other threads:[~2025-04-03 17:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-02 20:02 [PATCH 0/2] cifs: Revert bogus fix for CVE-2024-54680 and its followup commit Kuniyuki Iwashima
2025-04-02 20:02 ` [PATCH 1/2] Revert "smb: client: Fix netns refcount imbalance causing leaks and use-after-free" Kuniyuki Iwashima
2025-04-03 3:16 ` Wang Zhaolong
2025-04-03 9:59 ` Wang Zhaolong
2025-04-03 17:26 ` Kuniyuki Iwashima
2025-04-03 17:32 ` Steve French
2025-04-03 17:46 ` Kuniyuki Iwashima [this message]
2025-04-02 20:02 ` [PATCH 2/2] Revert "smb: client: fix TCP timers deadlock after rmmod" Kuniyuki Iwashima
2025-04-03 3:12 ` Wang Zhaolong
2025-04-03 1:14 ` [PATCH 0/2] cifs: Revert bogus fix for CVE-2024-54680 and its followup commit Steve French
2025-04-03 2:18 ` Kuniyuki Iwashima
2025-04-03 3:19 ` Steve French
2025-04-03 10:14 ` Wang Zhaolong
2025-04-11 7:04 ` Kuniyuki Iwashima
2025-04-12 17:28 ` Steve French
2025-04-12 19:10 ` Kuniyuki Iwashima
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=20250403174642.96094-1-kuniyu@amazon.com \
--to=kuniyu@amazon.com \
--cc=bharathsm@microsoft.com \
--cc=ematsumiya@suse.de \
--cc=kuni1840@gmail.com \
--cc=linux-cifs@vger.kernel.org \
--cc=pc@manguebit.com \
--cc=ronniesahlberg@gmail.com \
--cc=samba-technical@lists.samba.org \
--cc=sfrench@samba.org \
--cc=smfrench@gmail.com \
--cc=sprasad@microsoft.com \
--cc=tom@talpey.com \
--cc=wangzhaolong1@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