From: Sasha Levin <sashal@kernel.org>
To: Steve French <smfrench@gmail.com>
Cc: Stable <stable@vger.kernel.org>,
Greg KH <gregkh@linuxfoundation.org>,
CIFS <linux-cifs@vger.kernel.org>,
Namjae Jeon <linkinjeon@kernel.org>
Subject: Re: backport of missing fs/smb patches not in 6.6.30 stable
Date: Mon, 6 May 2024 19:11:30 -0400 [thread overview]
Message-ID: <Zjljol_GiXW3bKid@sashalap> (raw)
In-Reply-To: <CAH2r5mtC8NK=bH6qZfN6qwa=jot_scuLiDfYWSbFMwDWmkthOA@mail.gmail.com>
On Thu, May 02, 2024 at 11:28:38PM -0500, Steve French wrote:
>6.6.30-rc1 has a large set of fs/smb (cifs.ko and ksmbd.ko) patches
>backported but was missing more than 30 fixes so I put together a safe
>backport of the remaining, leaving out patches that had dependencies
>on things outside of fs/smb
>
>The following changes since commit 488f7008e62890fae8c7a2d3583913c8074f1fc6:
>
> smb3: fix lock ordering potential deadlock in cifs_sync_mid_result
>(2024-04-30 12:30:53 -0500)
>
>are available in the Git repository at:
>
> git://git.samba.org/ksmbd.git tags/6.6.30-rc1-full-fs-smb-backport
>
>for you to fetch changes up to 411b6f385ac2427ee9d70fae277a4ed6b9d3983f:
>
> smb: smb2pdu.h: Avoid -Wflex-array-member-not-at-end warnings
>(2024-05-01 02:18:25 -0500)
>
>----------------------------------------------------------------
>full backport for 6.6.30, includes all 80 (of the relevant) missing
>fs/smb changesets
>
>Test results look good (and better than without the patches). Here
>are the functional test results (they passed exhaustive set of tests
>to various server types):
>http://smb311-linux-testing.southcentralus.cloudapp.azure.com/#/builders/3/builds/99
>http://smb311-linux-testing.southcentralus.cloudapp.azure.com/#/builders/5/builds/117
>http://smb311-linux-testing.southcentralus.cloudapp.azure.com/#/builders/9/builds/51
>http://smb311-linux-testing.southcentralus.cloudapp.azure.com/#/builders/10/builds/63
>
>Note that 22 patches had dependencies and were not appropriate to
>backport and are not included, but here is the list of the additional
>80 fs/smb patches included, many of which fix bugs (the others reduce
>risk of backport, and help avoid merge conflicts):
>411b6f385ac2 (HEAD -> fs-smb-backport-linux-6.6.30-rc1, tag:
>6.6.30-rc1-full-fs-smb-backport,
>origin/fs-smb-backport-linux-6.6.30-rc1) smb: smb2pdu.h: Avoid
>-Wflex-array-member-not-at-end warnings
Thanks Steve, I'll pick these up.
In the future, if the patches don't need massaging, just a list of the
upstream commit ids would be great :)
--
Thanks,
Sasha
prev parent reply other threads:[~2024-05-06 23:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-03 4:28 backport of missing fs/smb patches not in 6.6.30 stable Steve French
2024-05-06 23:11 ` 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=Zjljol_GiXW3bKid@sashalap \
--to=sashal@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linkinjeon@kernel.org \
--cc=linux-cifs@vger.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).