From: Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>
To: kovalev@altlinux.org, stable@vger.kernel.org
Cc: abuehaze@amazon.com, smfrench@gmail.com, greg@kroah.com,
linux-cifs@vger.kernel.org, keescook@chromium.org,
darren.kenny@oracle.com, pc@manguebit.com,
nspmangalore@gmail.com, vegard.nossum@oracle.com
Subject: Re: [PATCH 5.10.y] cifs: fix off-by-one in SMB2_query_info_init()
Date: Mon, 29 Jan 2024 21:57:40 +0530 [thread overview]
Message-ID: <88f25b32-033c-4e1c-b1d5-18bbc2ec91c9@oracle.com> (raw)
In-Reply-To: <06bddf4e-a15f-bf1b-b9e5-d173cdacf4d0@basealt.ru>
Hi Kovalev,
On 29/01/24 1:49 pm, kovalev@altlinux.org wrote:
> 29.01.2024 08:43, Harshit Mogalapalli wrote:
>> This patch is only for v5.10.y stable kernel.
>> I have tested the patched kernel, after mounting it doesn't become
>> unavailable.
>>
>> Context:
>> [1]
>> https://lore.kernel.org/all/CAH2r5mv2ipr4KJfMDXwHgq9L+kGdnRd1C2svcM=PCoDjA7uALA@mail.gmail.com/#t
>>
>> Note to Greg: This is alternative way to fix by not taking commit
>> eb3e28c1e89b ("smb3: Replace smb2pdu 1-element arrays with
>> flex-arrays").
>> before applying this patch a patch in the queue needs to be removed:
>> https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/tree/queue-5.10/smb3-replace-smb2pdu-1-element-arrays-with-flex-arrays.patch
> Maybe I don't understand something, but isn't there a goal when fixing
> bugs to keep the code of stable branches with upstream code as much as
> possible? Otherwise, the following fixes will not be compatible..
I agree, but at the same time we also should observe this:
eb3e28c1e89b ("smb3: Replace smb2pdu 1-element arrays with flex-arrays")
is not in 5.15.y so we probably shouldn't queue it up for 5.10.y.
Ref from stable kernel rules document:
https://www.kernel.org/doc/html/v6.7/process/stable-kernel-rules.html#:~:text=When%20using%20option,to%205.15.y.
(Just above Option 1 description)
Thanks,
Harshit
>
next prev parent reply other threads:[~2024-01-29 16:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-29 5:43 [PATCH 5.10.y] cifs: fix off-by-one in SMB2_query_info_init() Harshit Mogalapalli
2024-01-29 8:19 ` kovalev
2024-01-29 16:27 ` Harshit Mogalapalli [this message]
2024-01-29 16:37 ` Greg KH
2024-01-29 16:52 ` Harshit Mogalapalli
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=88f25b32-033c-4e1c-b1d5-18bbc2ec91c9@oracle.com \
--to=harshit.m.mogalapalli@oracle.com \
--cc=abuehaze@amazon.com \
--cc=darren.kenny@oracle.com \
--cc=greg@kroah.com \
--cc=keescook@chromium.org \
--cc=kovalev@altlinux.org \
--cc=linux-cifs@vger.kernel.org \
--cc=nspmangalore@gmail.com \
--cc=pc@manguebit.com \
--cc=smfrench@gmail.com \
--cc=stable@vger.kernel.org \
--cc=vegard.nossum@oracle.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