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: <20231031-laienhaft-weshalb-bc27f8dacd9e@brauner>
Date:   Tue, 31 Oct 2023 11:33:43 +0100
From:   Christian Brauner <brauner@...nel.org>
To:     Richard Weinberger <richard@....at>
Cc:     Jan Kara <jack@...e.cz>, Miquel Raynal <miquel.raynal@...tlin.com>,
        Stephen Rothwell <sfr@...b.auug.org.au>,
        Richard Weinberger <richard.weinberger@...il.com>,
        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

On Tue, Oct 31, 2023 at 10:02:10AM +0100, Richard Weinberger wrote:
> Jan,
> 
> ----- Ursprüngliche Mail -----
> >> >>   1bcded92d938 ("mtd: block2mtd: Convert to bdev_open_by_dev/path()")
> >> > 
> >> > I haven't seen this commit, I was not Cc'ed.
> >> 
> >> Me neither. :-/
> > 
> > I'm sorry for that but I took the maintainers entry for BLOCK2MTD which is:
> > 
> > BLOCK2MTD DRIVER
> > M:      Joern Engel <joern@...ybastard.org>
> > L:      linux-mtd@...ts.infradead.org
> > S:      Maintained
> > F:      drivers/mtd/devices/block2mtd.c
> > 
> > And both Joern and linux-mtd were CCed on the patch. If different people
> > should be CCed these days, please update the entry. Thanks!
> 
> Ah, you did a manual lookup?
> Because get_maintainer.pl seems to do the right thing:
> 
> $ ./scripts/get_maintainer.pl drivers/mtd/devices/block2mtd.c
> Joern Engel <joern@...ybastard.org> (maintainer:BLOCK2MTD DRIVER)
> Miquel Raynal <miquel.raynal@...tlin.com> (maintainer:MEMORY TECHNOLOGY DEVICES (MTD))
> Richard Weinberger <richard@....at> (maintainer:MEMORY TECHNOLOGY DEVICES (MTD))
> Vignesh Raghavendra <vigneshr@...com> (maintainer:MEMORY TECHNOLOGY DEVICES (MTD))
> linux-mtd@...ts.infradead.org (open list:BLOCK2MTD DRIVER)
> linux-kernel@...r.kernel.org (open list)
>  
> >> >> 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.
> > 
> > Yes, that's one of the cases where stable rules make life harder for actual
> > fixes... You can try pushing ff6abbe85634 to stable even if it is not
> > upstream since it fixes a real bug and taking the upstream solution is
> > indeed IMO too intrusive. Sometimes stable maintainers accept such fixes.
> 
> Yep, let's try this route. :-)

Is there anything for me to do? IOW, do I need to grab that patch or
not? :)