linux-kernel - Re: [ovl] 30f9ef9479: BUG:kernel_NULL_pointer

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: <20220413073012.qwtlopbcbbkffaby@wittgenstein>
Date:   Wed, 13 Apr 2022 09:30:12 +0200
From:   Christian Brauner <brauner@...nel.org>
To:     Oliver Sang <oliver.sang@...el.com>
Cc:     Ammar Faizi <ammarfaizi2@...weeb.org>, lkp@...ts.01.org,
        lkp@...el.com, guobing.chen@...el.com, ming.a.chen@...el.com,
        frank.du@...el.com, Shuhua.Fan@...el.com, wangyang.guo@...el.com,
        Wenhuan.Huang@...el.com, jessica.ji@...el.com, shan.kang@...el.com,
        guangli.li@...el.com, tiejun.li@...el.com, yu.ma@...el.com,
        dapeng1.mi@...el.com, jiebin.sun@...el.com, gengxin.xie@...el.com,
        fan.zhao@...el.com, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [ovl]  30f9ef9479: BUG:kernel_NULL_pointer_dereference,address

On Mon, Apr 11, 2022 at 05:07:19PM +0800, Oliver Sang wrote:
> hi, Christian,
> 
> On Thu, Apr 07, 2022 at 12:26:05PM +0200, Christian Brauner wrote:
> > On Thu, Apr 07, 2022 at 05:40:23PM +0800, kernel test robot wrote:
> > > 
> > > 
> > > Greeting,
> > > 
> > > FYI, we noticed the following commit (built with gcc-11):
> > > 
> > > commit: 30f9ef94795008e5146f69d2eb043922a512bf85 ("ovl: support idmapped layers")
> > > https://github.com/ammarfaizi2/linux-block brauner/linux/fs.idmapped.overlayfs.v3
> > 
> > That's an old branch. :)
> > Anything that has a *.v<idx> appended is basically an old version in my
> > tree. The base branch is always the branch name without the *.v<idx>
> > suffix.
> 
> got it. so there is no need to test these *.v<idx> branches, whatever build,
> boot or function, right? If so, we will disable it.

Yeah, I maintain *.v<idx> branches around. Each time I need to send a
new version of a patchset I do:

git checkout -b base.branch.v<idx> base.branch

and then continue working on

git checkout base.branch

for the new version. :)

I try to make sure to only push base.branch to git.kernel.org once I
know it builds fine. Before that I only push to other code-hosting
platforms. One of the reasons being that I try to avoid upsetting the
various build bots. :)