The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Wang Zhaolong <wangzhaolong1@huawei.com>
Cc: Kuniyuki Iwashima <kuniyu@amazon.com>,
	edumazet@google.com, ematsumiya@suse.de,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-net@vger.kernel.org, smfrench@gmail.com,
	zhangchangzhong@huawei.com, cve@kernel.org, sfrench@samba.org
Subject: Re: Fwd: [PATCH][SMB3 client] fix TCP timers deadlock after rmmod
Date: Wed, 2 Apr 2025 08:13:36 +0100	[thread overview]
Message-ID: <2025040200-unchanged-roaming-52b3@gregkh> (raw)
In-Reply-To: <36dc113c-383e-4b8a-88c1-6a070e712086@huawei.com>

On Wed, Apr 02, 2025 at 12:49:50PM +0800, Wang Zhaolong wrote:
> Yes, it seems the previous description might not have been entirely clear.
> I need to clearly point out that this patch, intended as the fix for CVE-2024-54680,
> does not actually address any real issues. It also fails to resolve the null pointer
> dereference problem within lockdep. On top of that, it has caused a series of
> subsequent leakage issues.

If this cve does not actually fix anything, then we can easily reject
it, please just let us know if that needs to happen here.

thanks,

greg k-h

  reply	other threads:[~2025-04-02  7:15 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAH2r5msqxcvHcbDt0x_eNpbdPxUhgFoOAPchZ16EBZeFhCdAKA@mail.gmail.com>
2024-12-19  0:28 ` Fwd: [PATCH][SMB3 client] fix TCP timers deadlock after rmmod Steve French
2025-04-01 13:54   ` Wang Zhaolong
2025-04-01 20:26     ` Kuniyuki Iwashima
2025-04-02  0:57       ` Kuniyuki Iwashima
2025-04-02  4:43         ` Wang Zhaolong
2025-04-02  2:01     ` Kuniyuki Iwashima
2025-04-02  4:49       ` Wang Zhaolong
2025-04-02  7:13         ` Greg Kroah-Hartman [this message]
2025-04-02  9:15           ` Wang Zhaolong
2025-04-02 15:18             ` Greg Kroah-Hartman
2025-04-02 20:09               ` Kuniyuki Iwashima
2025-04-02 20:15                 ` Greg KH
2025-04-02 20:22                   ` Kuniyuki Iwashima
2025-04-02 20:28                     ` Greg KH
2025-04-02 20:50                       ` Kuniyuki Iwashima
2025-04-02 21:32                         ` Greg KH
2025-04-02 21:58                           ` 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=2025040200-unchanged-roaming-52b3@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=cve@kernel.org \
    --cc=edumazet@google.com \
    --cc=ematsumiya@suse.de \
    --cc=kuniyu@amazon.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-net@vger.kernel.org \
    --cc=sfrench@samba.org \
    --cc=smfrench@gmail.com \
    --cc=wangzhaolong1@huawei.com \
    --cc=zhangchangzhong@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