linux-kernel - Re: [syzbot] linux-next test error: KASAN: null-ptr-deref Read in fuse_conn

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 for Android: free password hash cracker in your pocket

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

Date:   Mon, 6 Sep 2021 19:40:37 +0200
From:   Marco Elver <elver@...gle.com>
To:     Miklos Szeredi <miklos@...redi.hu>
Cc:     syzbot <syzbot+b304e8cb713be5f9d4e1@...kaller.appspotmail.com>,
        linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
        Linux-Next Mailing List <linux-next@...r.kernel.org>,
        Stephen Rothwell <sfr@...b.auug.org.au>,
        syzkaller-bugs <syzkaller-bugs@...glegroups.com>
Subject: Re: [syzbot] linux-next test error: KASAN: null-ptr-deref Read in fuse_conn_put

On Mon, 6 Sept 2021 at 19:35, Miklos Szeredi <miklos@...redi.hu> wrote:
>
> On Mon, 6 Sept 2021 at 18:59, Marco Elver <elver@...gle.com> wrote:
> >
> > On Mon, 6 Sept 2021 at 13:56, Miklos Szeredi <miklos@...redi.hu> wrote:
> > > Thanks,
> > >
> > > Force pushed fixed commit 660585b56e63 ("fuse: wait for writepages in
> > > syncfs") to fuse.git#for-next.
> > >
> > > This is fixed as far as I'm concerned, not sure how to tell that to syzbot.
> >
> > Thanks -- we can let syzbot know:
> >
> > #syz fix: fuse: wait for writepages in syncfs
> >
> > (The syntax is just "#syz fix: <commit title>".)
>
> Yeah, but that patch has several versions, one of which is broken.
> Syzbot can't tell the difference just based on the title.

True, and a general problem with trying to track -next, where even
commit hashes might change. For -next, we can probably live with just
marking the problem fixed, meaning anyone checking the issue will see
a fix exists (and not invest time in trying to fix it).

If the problem persists, syzbot will just keep complaining. ;-)