From: Kees Cook <keescook@chromium.org>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: syzbot <syzbot+c4dcac91687a29cbae15@syzkaller.appspotmail.com>,
keun-o.park@darkmatter.ae, Laura Abbott <labbott@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
Linux-MM <linux-mm@kvack.org>,
Mark Rutland <mark.rutland@arm.com>,
Ingo Molnar <mingo@kernel.org>,
syzkaller-bugs@googlegroups.com
Subject: Re: WARNING: bad usercopy in put_cmsg
Date: Wed, 7 Feb 2018 06:16:51 +1100 [thread overview]
Message-ID: <CAGXu5j+n8XCAwsRzDRoaxRqDEH9byMB=6e5FxPW=1mrGoUzRRQ@mail.gmail.com> (raw)
In-Reply-To: <CACT4Y+ZybLXnPiQ8BDLORD6VA8E7KeMrJZxO8q46MfMKyH7q_Q@mail.gmail.com>
On Wed, Feb 7, 2018 at 4:33 AM, Dmitry Vyukov <dvyukov@google.com> wrote:
> On Tue, Feb 6, 2018 at 6:31 PM, syzbot
> <syzbot+c4dcac91687a29cbae15@syzkaller.appspotmail.com> wrote:
>> Hello,
>>
>> syzbot hit the following crash on upstream commit
>> e237f98a9c134c3d600353f21e07db915516875b (Mon Feb 5 21:35:56 2018 +0000)
>> Merge tag 'xfs-4.16-merge-5' of
>> git://git.kernel.org/pub/scm/fs/xfs/xfs-linux
>>
>> So far this crash happened 8 times on net-next, upstream.
>> C reproducer is attached.
>> syzkaller reproducer is attached.
>> Raw console output is attached.
>> compiler: gcc (GCC) 7.1.1 20170620
>> .config is attached.
>
> #syz dup: WARNING in usercopy_warn
>
> Let's make that one the main copy, since Kees is already looking at it.
This one has a more descriptive subject, can we dup towards this one?
Whatever the case, yup, still working on it.
-Kees
--
Kees Cook
Pixel Security
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2018-02-06 19:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-06 17:31 syzbot
2018-02-06 17:33 ` Dmitry Vyukov
2018-02-06 19:16 ` Kees Cook [this message]
2018-02-07 13:55 ` Dmitry Vyukov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAGXu5j+n8XCAwsRzDRoaxRqDEH9byMB=6e5FxPW=1mrGoUzRRQ@mail.gmail.com' \
--to=keescook@chromium.org \
--cc=dvyukov@google.com \
--cc=keun-o.park@darkmatter.ae \
--cc=labbott@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mark.rutland@arm.com \
--cc=mingo@kernel.org \
--cc=syzbot+c4dcac91687a29cbae15@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox