[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20201114070025.GO3576660@ZenIV.linux.org.uk>
Date: Sat, 14 Nov 2020 07:00:25 +0000
From: Al Viro <viro@...iv.linux.org.uk>
To: Nathan Chancellor <natechancellor@...il.com>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Christoph Hellwig <hch@....de>,
Greg KH <gregkh@...uxfoundation.org>,
Alexey Dobriyan <adobriyan@...il.com>,
linux-fsdevel <linux-fsdevel@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
kys@...rosoft.com, haiyangz@...rosoft.com, sthemmin@...rosoft.com,
wei.liu@...nel.org, linux-hyperv@...r.kernel.org
Subject: Re: [PATCH 1/6] seq_file: add seq_read_iter
On Fri, Nov 13, 2020 at 11:19:34PM -0700, Nathan Chancellor wrote:
> Assuming so, I have attached the output both with and without the
> WARN_ON. Looks like mountinfo is what is causing the error?
Cute... FWIW, on #origin + that commit with fix folded in I don't
see anything unusual in reads from mountinfo ;-/ OTOH, they'd
obviously been... creative with readv(2) arguments, so it would
be very interesting to see what it is they are passing to it.
I'm half-asleep right now; will try to cook something to gather
that information tomorrow morning. 'Later...
Powered by blists - more mailing lists