From: Greg KH <gregkh@linuxfoundation.org>
To: Namjae Jeon <linkinjeon@kernel.org>
Cc: sashal@kernel.org, stable@vger.kernel.org, smfrench@gmail.com
Subject: Re: [PATCH v2 5.15.y 0/8] Additional ksmbd backport patches for linux-5.15.y
Date: Sat, 30 Dec 2023 11:04:12 +0000 [thread overview]
Message-ID: <2023123044-creamer-connected-32d8@gregkh> (raw)
In-Reply-To: <20231227102605.4766-1-linkinjeon@kernel.org>
On Wed, Dec 27, 2023 at 07:25:57PM +0900, Namjae Jeon wrote:
> These patches are backport patches to support directory(v2) lease and
> additional bug fixes for linux-5.15.y.
> note that 0001 patch add a dependency on cifs ARC4 omitted from
> backporting commit f9929ef6a2a5("ksmbd: add support for key exchange").
>
> Namjae Jeon (8):
> ksmbd: have a dependency on cifs ARC4
> ksmbd: set epoch in create context v2 lease
> ksmbd: set v2 lease capability
> ksmbd: downgrade RWH lease caching state to RH for directory
> ksmbd: send v2 lease break notification for directory
> ksmbd: lazy v2 lease break on smb2_write()
> ksmbd: avoid duplicate opinfo_put() call on error of
> smb21_lease_break_ack()
> ksmbd: fix wrong allocation size update in smb2_open()a
We can't just take these for 5.15.y, they also need to be in the newer
stable releases as well, right? Please send patch series for them also
and then we can take these.
thanks,
greg k-h
next prev parent reply other threads:[~2023-12-30 11:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-27 10:25 [PATCH v2 5.15.y 0/8] Additional ksmbd backport patches for linux-5.15.y Namjae Jeon
2023-12-27 10:25 ` [PATCH v2 5.15.y 1/8] ksmbd: have a dependency on cifs ARC4 Namjae Jeon
2023-12-27 10:25 ` [PATCH v2 5.15.y 2/8] ksmbd: set epoch in create context v2 lease Namjae Jeon
2023-12-27 10:26 ` [PATCH v2 5.15.y 3/8] ksmbd: set v2 lease capability Namjae Jeon
2023-12-27 10:26 ` [PATCH v2 5.15.y 4/8] ksmbd: downgrade RWH lease caching state to RH for directory Namjae Jeon
2023-12-27 10:26 ` [PATCH v2 5.15.y 5/8] ksmbd: send v2 lease break notification " Namjae Jeon
2023-12-27 10:26 ` [PATCH v2 5.15.y 6/8] ksmbd: lazy v2 lease break on smb2_write() Namjae Jeon
2023-12-27 10:26 ` [PATCH v2 5.15.y 7/8] ksmbd: avoid duplicate opinfo_put() call on error of smb21_lease_break_ack() Namjae Jeon
2023-12-27 10:26 ` [PATCH v2 5.15.y 8/8] ksmbd: fix wrong allocation size update in smb2_open() Namjae Jeon
2023-12-30 11:04 ` Greg KH [this message]
2023-12-30 13:53 ` [PATCH v2 5.15.y 0/8] Additional ksmbd backport patches for linux-5.15.y Namjae Jeon
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=2023123044-creamer-connected-32d8@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=linkinjeon@kernel.org \
--cc=sashal@kernel.org \
--cc=smfrench@gmail.com \
--cc=stable@vger.kernel.org \
/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