linux-kernel - Re: general protection fault in __x86_indirect_thunk

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: <CACT4Y+ZwfyCjT_UBq4FwXd8SkmktBXqDFKM87x5fbstYJe4YuA@mail.gmail.com>
Date:   Thu, 21 Mar 2019 07:16:35 +0100
From:   Dmitry Vyukov <dvyukov@...gle.com>
To:     NeilBrown <neilb@...e.com>
Cc:     syzbot <syzbot+83e12cf81d2c14842146@...kaller.appspotmail.com>,
        Bruce Fields <bfields@...ldses.org>,
        Jeff Layton <jlayton@...nel.org>,
        linux-fsdevel <linux-fsdevel@...r.kernel.org>,
        LKML <linux-kernel@...r.kernel.org>,
        syzkaller-bugs <syzkaller-bugs@...glegroups.com>,
        Al Viro <viro@...iv.linux.org.uk>
Subject: Re: general protection fault in __x86_indirect_thunk_rbx

On Thu, Mar 21, 2019 at 7:08 AM NeilBrown <neilb@...e.com> wrote:
>
> On Wed, Mar 20 2019, syzbot wrote:
>
> > syzbot has bisected this bug to:
> >
> > commit dee160df820de41ff2f59a715643680822a0ab06
> > Author: NeilBrown <neilb@...e.com>
> > Date:   Mon Nov 5 01:30:47 2018 +0000
> >
> >      locks: use properly initialized file_lock when unlocking.
>
> This commit did not make it to mainline.
> It was replaced by
>
> Commit d6367d624137 ("fs/locks: use properly initialized file_lock when unlocking.")
>
> which added a call to locks_init_lock() in flock_make_lock().
>
> NeilBrown

Hi Neil,

You are talking to robot. Robot does not understand English prose ;)
Here is info on how to talk to it:
> See https://goo.gl/tpsmEJ for more information about syzbot.

In this case I think we need to say:

#syz fix: fs/locks: use properly initialized file_lock when unlocking.

> > bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=13f39fd7200000
> > start commit:   dee160df locks: use properly initialized file_lock when un..
> > git tree:       linux-next
> > final crash:    https://syzkaller.appspot.com/x/report.txt?x=100b9fd7200000
> > console output: https://syzkaller.appspot.com/x/log.txt?x=17f39fd7200000
> > kernel config:  https://syzkaller.appspot.com/x/.config?x=caa433e1c8778437
> > dashboard link: https://syzkaller.appspot.com/bug?extid=83e12cf81d2c14842146
> > syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=15bd9447400000
> > C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=1121d82b400000
> >
> > Reported-by: syzbot+83e12cf81d2c14842146@...kaller.appspotmail.com
> > Fixes: dee160df ("locks: use properly initialized file_lock when
> > unlocking.")
>
> --
> You received this message because you are subscribed to the Google Groups "syzkaller-bugs" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller-bugs+unsubscribe@...glegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/syzkaller-bugs/87lg187oao.fsf%40notabene.neil.brown.name.
> For more options, visit https://groups.google.com/d/optout.