linux-kernel - Re: [PATCH] signal: Don't send signals to tasks that don't exist

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]

Date:   Sat, 18 Aug 2018 00:51:14 -0500
From:   ebiederm@...ssion.com (Eric W. Biederman)
To:     Andrew Morton <akpm@...ux-foundation.org>
Cc:     Dmitry Vyukov <dvyukov@...gle.com>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        Oleg Nesterov <oleg@...hat.com>,
        LKML <linux-kernel@...r.kernel.org>,
        Wen Yang <wen.yang99@....com.cn>,
        majiang <ma.jiang@....com.cn>,
        "J. Bruce Fields" <bfields@...ldses.org>,
        syzkaller-bugs <syzkaller-bugs@...glegroups.com>,
        Andrey Vagin <avagin@...tuozzo.com>,
        Cyrill Gorcunov <gorcunov@...il.com>
Subject: Re: [PATCH] signal: Don't send signals to tasks that don't exist

Andrew Morton <akpm@...ux-foundation.org> writes:

> Dude, lighten up.

This was in response to being asked by a the maintainers of a bot that has
wasted copious quanties of my time to please not waste their time.

To prevent the wasting of time it was requested that when syzbot would
be enabled on linux-next again that it only report issues when there is
a reproducer, and it can narrow the issue down to at least the branch in
linux-next the issue occured on.  I thought there was general agreement
on that point.

That very much did not happen in this case.  So I heard a request to not
waste the time of a bot from people who have not taken what appear to be
reasonable steps to not waste my time.

I am especially annoyed that the bot despite having a reproducer was not
able to at least narrow it down to the branch in linux-next.

I was dismayed when I saw the syzbot report triggered someone to remove
themselves from MAINTAINERS.

Further I actually received a bug report (not found one by luck when I
was skimming through a mailing list) from another group of people whose
automated testing also found the issue and were able to succesfully root
cause the issue.  So I know good but reports are possible on this issue.

In short.  I have been burned by syzbot.  I don't see evidence of change.
I am grumpy.

Eric