[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1337e3ea-6984-7f70-98cc-f20a43e659d2@quicinc.com>
Date: Thu, 10 Jun 2021 15:08:19 -0400
From: Qian Cai <quic_qiancai@...cinc.com>
To: Al Viro <viro@...iv.linux.org.uk>
CC: Linus Torvalds <torvalds@...ux-foundation.org>,
<linux-fsdevel@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
David Sterba <dsterba@...e.com>,
Miklos Szeredi <miklos@...redi.hu>,
Anton Altaparmakov <anton@...era.com>,
David Howells <dhowells@...hat.com>,
Matthew Wilcox <willy@...radead.org>,
Pavel Begunkov <asml.silence@...il.com>
Subject: Re: [RFC][PATCHSET] iov_iter work
On 6/10/2021 11:35 AM, Al Viro wrote:
> On Thu, Jun 10, 2021 at 10:29:59AM -0400, Qian Cai wrote:
>
>> Al, a quick fuzzing on today's linux-next triggered this. I never saw this before, so I am wondering if this is anything to do with this series. I could try to narrow it down and bisect if necessary. Any thoughts?
>
> Do you have a reproducer?
I have no idea how reproducible this is, but it was triggered by running the fuzzing within a half-hour.
$ trinity -C 16
> call of memcpy_from_skb(), calling copy_from_iter_full(), which
> calls iov_iter_revert() on failure now...
>
> Bloody hell. Incremental, to be folded in:
This patch is running good so far. I'll report back if things changed.
Powered by blists - more mailing lists