All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: gregkh@linuxfoundation.org, stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>,
	linux-kernel@vger.kernel.org, linkinjeon@kernel.org,
	stfrench@microsoft.com, d.ornaghi97@gmail.com,
	knavaneeth786@gmail.com, charsyam@gmail.com,
	Alva Lan <alvalan9@foxmail.com>
Subject: Re: [PATCH 6.6.y v3 0/4] ksmbd: validate owner of durable handle on reconnect
Date: Tue, 26 May 2026 09:38:14 -0400	[thread overview]
Message-ID: <20260526140000.agent5-0002@kernel.org> (raw)
In-Reply-To: <tencent_03EB621C56988886195ADF9AA78F33494007@qq.com>

On Tue, May 26, 2026 at 03:57:01PM +0800, Alva Lan wrote:
> This series backports the fix for CVE-2026-31717 along with the two
> prerequisite commits and the follow-up that closes the scavenger
> races (KASAN-validated).

Queued the full v3 series (all four patches) for 6.6, thanks.

-- 
Thanks,
Sasha

      parent reply	other threads:[~2026-05-26 13:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-26  7:57 [PATCH 6.6.y v3 0/4] ksmbd: validate owner of durable handle on reconnect Alva Lan
2026-05-26  7:58 ` [PATCH 6.6.y v3 1/4] ksmbd: avoid reclaiming expired durable opens by the client Alva Lan
     [not found] ` <20260526075843.50277-1-alvalan9@foxmail.com>
2026-05-26  7:58   ` [PATCH 6.6.y v3 2/4] ksmbd: add durable scavenger timer Alva Lan
2026-05-26  7:58   ` [PATCH 6.6.y v3 3/4] ksmbd: validate owner of durable handle on reconnect Alva Lan
2026-05-26  7:58   ` [PATCH 6.6.y v3 4/4] ksmbd: close durable scavenger races against m_fp_list lookups Alva Lan
2026-05-26 13:38 ` Sasha Levin [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=20260526140000.agent5-0002@kernel.org \
    --to=sashal@kernel.org \
    --cc=alvalan9@foxmail.com \
    --cc=charsyam@gmail.com \
    --cc=d.ornaghi97@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=knavaneeth786@gmail.com \
    --cc=linkinjeon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=stfrench@microsoft.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.