* Backport smb client char/block fixes
@ 2024-10-28 9:43 Pali Rohár
2024-11-01 23:56 ` Pali Rohár
0 siblings, 1 reply; 3+ messages in thread
From: Pali Rohár @ 2024-10-28 9:43 UTC (permalink / raw)
To: stable; +Cc: Steve French, Paulo Alcantara
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Backport smb client char/block fixes
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
0 siblings, 1 reply; 3+ messages in thread
From: Pali Rohár @ 2024-11-01 23:56 UTC (permalink / raw)
To: Greg Kroah-Hartman, Sasha Levin; +Cc: Steve French, Paulo Alcantara, stable
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Backport smb client char/block fixes
2024-11-01 23:56 ` Pali Rohár
@ 2024-11-02 22:26 ` Sasha Levin
0 siblings, 0 replies; 3+ messages in thread
From: Sasha Levin @ 2024-11-02 22:26 UTC (permalink / raw)
To: Pali Rohár; +Cc: Greg Kroah-Hartman, Steve French, Paulo Alcantara, stable
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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2024-11-02 22:26 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 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 NNTP newsgroup(s).