[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <db42c87ba2c5b0852ad42ba51792ee67ab036a37.camel@hammerspace.com>
Date: Thu, 12 Sep 2019 13:25:53 +0000
From: Trond Myklebust <trondmy@...merspace.com>
To: "bfields@...ldses.org" <bfields@...ldses.org>,
"bcodding@...hat.com" <bcodding@...hat.com>
CC: "tibbs@...h.uh.edu" <tibbs@...h.uh.edu>,
"linux@...m.de" <linux@...m.de>,
"linux-nfs@...r.kernel.org" <linux-nfs@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"km@...all.com" <km@...all.com>,
"chuck.lever@...cle.com" <chuck.lever@...cle.com>
Subject: Re: Regression in 5.1.20: Reading long directory fails
On Thu, 2019-09-12 at 09:13 -0400, J. Bruce Fields wrote:
> (Unless I'm missing something. I haven't looked at this code in a
> while. Though it was problem me that wrote it originally--apologies
> for
> that....)
>
The function itself is fine. It was just the name I'm objecting to,
since we're actually moving the last 'n' bytes in the message in order
to be able to read them.
--
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@...merspace.com
Powered by blists - more mailing lists