From: Sasha Levin <sashal@kernel.org>
To: "Pali Rohár" <pali@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Steve French <stfrench@microsoft.com>,
Paulo Alcantara <pc@manguebit.com>,
stable@vger.kernel.org
Subject: Re: Backport smb client char/block fixes
Date: Sat, 2 Nov 2024 18:26:25 -0400 [thread overview]
Message-ID: <ZyanEXGIv7l48n04@sashalap> (raw)
In-Reply-To: <20241101235645.yqwqqipzhzoyprch@pali>
On Sat, Nov 02, 2024 at 12:56:45AM +0100, Pali Rohár wrote:
>Hello Greg and Sasha, do you have any opinion about this?
>
>On Monday 28 October 2024 10:43:39 Pali Rohár wrote:
>> Hello,
>>
>> I would like to propose backporting these two commits into stable:
>> * 663f295e3559 ("smb: client: fix parsing of device numbers")
>> * a9de67336a4a ("smb: client: set correct device number on nfs reparse points")
>>
>> Linux SMB client without these two recent fixes swaps device major and
>> minor numbers, which makes basically char/block device nodes unusable.
>>
>> Commit 663f295e3559 ("smb: client: fix parsing of device numbers")
>> should have had following Fixes line:
>> Fixes: 45e724022e27 ("smb: client: set correct file type from NFS reparse points")
>>
>> And commit a9de67336a4a ("smb: client: set correct device number on nfs
>> reparse points") should have contained line:
>> Fixes: 102466f303ff ("smb: client: allow creating special files via reparse points")
>>
>> Pali
I'll queue both for 6.11 and 6.6, thanks!
--
Thanks,
Sasha
prev parent reply other threads:[~2024-11-02 22:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-28 9:43 Backport smb client char/block fixes Pali Rohár
2024-11-01 23:56 ` Pali Rohár
2024-11-02 22:26 ` 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=ZyanEXGIv7l48n04@sashalap \
--to=sashal@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=pali@kernel.org \
--cc=pc@manguebit.com \
--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.