From: Al Viro <viro@ZenIV.linux.org.uk>
To: Joseph Bisch <joseph.bisch@hpe.com>
Cc: linux-fsdevel@vger.kernel.org, ajames@hpe.com,
syzkaller@googlegroups.com, lkml@vger.kernel.org
Subject: Re: kernel BUG at fs/direct-io.c:211! in next-20160930
Date: Wed, 5 Oct 2016 23:04:02 +0100 [thread overview]
Message-ID: <20161005220401.GG19539@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20161005210345.GA3192@hpe.com>
On Wed, Oct 05, 2016 at 03:03:46PM -0600, Joseph Bisch wrote:
> While fuzzing next-20160930 with syzkaller I encountered the following:
>
> kernel BUG at fs/direct-io.c:211!
> invalid opcode: 0000 [#1] SMP
Should've been fixed in current -next - it's handling of iov_iter_get_pages()
n ITER_PIPE iterators when they get full; the things to watch for are
a) __pipe_get_pages() containing
size_t n = push_pipe(i, maxsize, &idx, start);
if (!n)
return -EFAULT;
and
b) "consistent treatment of EFAULT on O_DIRECT read/write" applied in
fs/direct-io.c
prev parent reply other threads:[~2016-10-05 22:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-05 21:03 kernel BUG at fs/direct-io.c:211! in next-20160930 Joseph Bisch
2016-10-05 22:04 ` Al Viro [this message]
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=20161005220401.GG19539@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=ajames@hpe.com \
--cc=joseph.bisch@hpe.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lkml@vger.kernel.org \
--cc=syzkaller@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 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.