linux-kernel - Re: linux-next: manual merge of the mtd tree with the vfs-brauner tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1541110626.24818.1698696696387.JavaMail.zimbra@nod.at>
Date:   Mon, 30 Oct 2023 21:11:36 +0100 (CET)
From:   Richard Weinberger <richard@....at>
To:     Miquel Raynal <miquel.raynal@...tlin.com>
Cc:     Stephen Rothwell <sfr@...b.auug.org.au>,
        Richard Weinberger <richard.weinberger@...il.com>,
        Christian Brauner <brauner@...nel.org>,
        Jan Kara <jack@...e.cz>,
        linux-kernel <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: manual merge of the mtd tree with the vfs-brauner
 tree

----- Ursprüngliche Mail -----
> Von: "Miquel Raynal" <miquel.raynal@...tlin.com>
>> Today's linux-next merge of the mtd tree got a conflict in:
>> 
>>   drivers/mtd/devices/block2mtd.c
>> 
>> between commit:
>> 
>>   1bcded92d938 ("mtd: block2mtd: Convert to bdev_open_by_dev/path()")
> 
> I haven't seen this commit, I was not Cc'ed.

Me neither. :-/
 
>> from the vfs-brauner tree and commit:
>> 
>>   ff6abbe85634 ("mtd: block2mtd: Add a valid holder to blkdev_put()")
> 
> I will drop this commit from mtd/next. Please take it through the
> vfs-brauner tree as well to avoid conflicts or otherwise, Richard, can
> you send an update at -rc1?

A side effect of 1bcded92d938 ("mtd: block2mtd: Convert to bdev_open_by_dev/path()")
is that it fixes the problem too. That's a good thing.

I'm a bit puzzled how to fix the problem for 6.5.y and 6.6.y stable releases.
Back porting 1bcded92d938 seems risky to me since the commit is large.
On the other hand, ff6abbe85634 will not make it into Linus' tree and therefore
is not suitable for stable either.

Thanks,
//richard