linux-kernel - Re: [PATCH AUTOSEL 5.10 16/27] btrfs: tree-checker: check item_size for dev

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] [day] [month] [year] [list]

Message-ID: <20220223172058.GR12643@twin.jikos.cz>
Date:   Wed, 23 Feb 2022 18:20:58 +0100
From:   David Sterba <dsterba@...e.cz>
To:     Su Yue <l@...enly.su>
Cc:     Greg KH <greg@...ah.com>, Sasha Levin <sashal@...nel.org>,
        linux-kernel@...r.kernel.org, stable@...r.kernel.org,
        David Sterba <dsterba@...e.com>, clm@...com,
        josef@...icpanda.com, linux-btrfs@...r.kernel.org
Subject: Re: [PATCH AUTOSEL 5.10 16/27] btrfs: tree-checker: check item_size
 for dev_item

On Fri, Feb 18, 2022 at 07:25:20PM +0800, Su Yue wrote:
> On Fri 18 Feb 2022 at 11:36, Greg KH <greg@...ah.com> wrote:
> > On Wed, Feb 09, 2022 at 01:40:52PM -0500, Sasha Levin wrote:
>  \
>       |                                    ~~~~~~~~~~~~^
> fs/btrfs/ctree.h:1833:1: note: in expansion of macro 
> \342\200\230BTRFS_SETGET_FUNCS\342\200\231
>  1833 | BTRFS_SETGET_FUNCS(item_size, struct btrfs_item, size, 
>  32);
>       | ^~~~~~~~~~~~~~~~~~
> ========================================================================
> 
> The upstream patchset[1] merged in 5.17-rc1, changed second 
> parameter
> of btrfs_item_size() from btrfs_item * to int directly.
> So yes, the backport is wrong.
> 
> I'm not familiar with stable backport progress. Should I file a 
> patch
> using btrfs_item *? Or just drop it?
> 
> The patch is related to  0c982944af27d131d3b74242f3528169f66950ad 
> but
> I wonder why the 0c98294 is not selected automatically.

We don't rely on the automatic selection, I evaluate all patches for
stable inclusion and add the CC: tag, this works well. Not all patches
need to go to stable, but AUTOSEL sometimes picks patches that could be
there and if it's not entirely wrong I don't object.