From: Kees Cook <keescook@chromium.org>
To: syzbot <syzbot+21cfe1f803e0e158acf1@syzkaller.appspotmail.com>
Cc: 00moses.alexander00@gmail.com, axboe@kernel.dk,
bvanassche@acm.org, hare@suse.com, hch@lst.de,
idryomov@gmail.com, joseph.qi@linux.alibaba.com,
jthumshirn@suse.de, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org, ming.lei@redhat.com,
sagi@grimberg.me, snitzer@redhat.com,
syzkaller-bugs@googlegroups.com, tj@kernel.org,
torvalds@linux-foundation.org, wgh@torlan.ru,
zkabelac@redhat.com
Subject: Re: WARNING in generic_make_request_checks
Date: Wed, 27 Nov 2019 11:26:19 -0800 [thread overview]
Message-ID: <201911271124.F01A0B37@keescook> (raw)
In-Reply-To: <00000000000085ce5905984f2c8b@google.com>
On Tue, Nov 26, 2019 at 11:45:00PM -0800, syzbot wrote:
> Hello,
>
> syzbot has tested the proposed patch and the reproducer did not trigger
> crash:
>
> Reported-and-tested-by:
> syzbot+21cfe1f803e0e158acf1@syzkaller.appspotmail.com
>
> Tested on:
>
> commit: 8b2ded1c block: don't warn when doing fsync on read-only d..
> git tree:
> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> kernel config: https://syzkaller.appspot.com/x/.config?x=d727e10a28207217
> dashboard link: https://syzkaller.appspot.com/bug?extid=21cfe1f803e0e158acf1
> compiler: gcc (GCC) 9.0.0 20181231 (experimental)
>
> Note: testing is done by a robot and is best-effort only.
It seems for successful tests, I still need to tell syzbot that this is
fixed?
#syz fix: block: don't warn when doing fsync on read-only devices
--
Kees Cook
next prev parent reply other threads:[~2019-11-27 19:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-09 3:39 WARNING in generic_make_request_checks syzbot
2019-11-22 12:05 ` syzbot
2019-11-27 4:54 ` Kees Cook
2019-11-27 7:45 ` syzbot
2019-11-27 19:26 ` Kees Cook [this message]
2019-11-28 8:52 ` 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=201911271124.F01A0B37@keescook \
--to=keescook@chromium.org \
--cc=00moses.alexander00@gmail.com \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=hare@suse.com \
--cc=hch@lst.de \
--cc=idryomov@gmail.com \
--cc=joseph.qi@linux.alibaba.com \
--cc=jthumshirn@suse.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=sagi@grimberg.me \
--cc=snitzer@redhat.com \
--cc=syzbot+21cfe1f803e0e158acf1@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tj@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=wgh@torlan.ru \
--cc=zkabelac@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.