linux-kernel - Re: general protection fault in send_sigurg_to

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: <20180815203503.GB30591@fieldses.org>
Date:   Wed, 15 Aug 2018 16:35:03 -0400
From:   "J. Bruce Fields" <bfields@...ldses.org>
To:     Dmitry Vyukov <dvyukov@...gle.com>
Cc:     Stephen Rothwell <sfr@...b.auug.org.au>,
        syzbot <syzbot+1f371ca19b341a276761@...kaller.appspotmail.com>,
        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 send_sigurg_to_task

On Tue, Aug 14, 2018 at 01:50:20PM -0700, Dmitry Vyukov wrote:
> On Tue, Aug 14, 2018 at 12:11 PM, J. Bruce Fields <bfields@...ldses.org> wrote:
> > On Mon, Aug 13, 2018 at 06:33:02AM -0700, syzbot wrote:
> >> syzbot has found a reproducer for the following crash on:
> >>
> >> HEAD commit:    5ed5da74de9e Add linux-next specific files for 20180813
> >> git tree:       linux-next
> >
> > I fetched linux-next but don't have 5ed5da74de9e.
> 
> Hi Bruce,
> 
> +Stephen for the disappeared linux-next commit.
> 
> On the dashboard link you can see that it also happened on a more
> recent commit 4e8b38549b50459a22573d756dd1f4e1963c2a8d that I do see
> now in linux-next.
> 
> > I'm also not sure why I'm on the cc for this.
> 
> You've been pointed to by "./scripts/get_maintainer.pl -f fs/fcntl.c"
> as maintainer of the file, which is the file where the crash happened.

We should probably fix that.  There's a tiny bit of lock-related code in
that file but it's not at all interesting compared, say, to the code
that this bug is hitting....

(Which I have no clue about.  send_sigurg_to_task() is getting a bad
task?  Help.)

--b.

diff --git a/MAINTAINERS b/MAINTAINERS
index 9d5eeff51b5f..a5dca2be8513 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -5541,9 +5541,6 @@ M:	Jeff Layton <jlayton@...nel.org>
 M:	"J. Bruce Fields" <bfields@...ldses.org>
 L:	linux-fsdevel@...r.kernel.org
 S:	Maintained
-F:	include/linux/fcntl.h
-F:	include/uapi/linux/fcntl.h
-F:	fs/fcntl.c
 F:	fs/locks.c
 
 FILESYSTEMS (VFS and infrastructure)