[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <78AC8FB0-86F3-4ABB-B2A9-2252CBFB4BC5@primarydata.com>
Date: Mon, 20 Jun 2016 14:54:36 +0000
From: Trond Myklebust <trondmy@...marydata.com>
To: Viro Alexander <viro@...iv.linux.org.uk>
CC: Oleg Drokin <green@...uxhacker.ru>,
Fields Bruce <bfields@...hat.com>,
linux-nfs list <linux-nfs@...r.kernel.org>,
"<linux-kernel@...r.kernel.org> Mailing List"
<linux-kernel@...r.kernel.org>,
"<linux-fsdevel@...r.kernel.org>" <linux-fsdevel@...r.kernel.org>
Subject: Re: NFS/d_splice_alias breakage
> On Jun 20, 2016, at 10:08, Al Viro <viro@...iv.linux.org.uk> wrote:
>
> On Mon, Jun 20, 2016 at 09:25:12AM -0400, Oleg Drokin wrote:
>> It looks like this patch was totally forgotten?
>> I don't see it in neither vfs nor nfs trees and yet it fixes a very easy to cause
>> crash in nfs code. And I think it's unrelated to the other parallel case too.
>
> I assumed it would go through NFS tree, seeing that it's NFS-specific and
> has nothing to do with any of the recent VFS changes (oops is triggerable
> starting from 3.11); I can certainly put it through vfs.git, and there
> will be changes nearby, but this one should go into -stable as a separate
> patch.
>
I’ll take it through the NFS tree.
Cheers
Trond
Powered by blists - more mailing lists