LKML Archive on
help / color / mirror / Atom feed
From: Nick Bowler <>
To: Olga Kornievskaia <>
Cc: Trond Myklebust <>,
	"" <>,
	"" <>,
	"" <>
Subject: Re: PROBLEM: oops spew with Linux 5.1.5 (NFS regression?)
Date: Mon, 3 Jun 2019 14:09:41 -0400	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 2019-06-03, Nick Bowler <> wrote:
> On 2019-05-29, Olga Kornievskaia <> wrote:
>> On Wed, May 29, 2019 at 1:14 PM Trond Myklebust <>
>>> OK, I think this is the same problem that Olga was seeing (Cced), and
>>> it looks like I missed the use-after-free issue when the server returns
>>> a credential error when she asked.
>> I think this is actually different than what I encountered for the
>> umount case but the trigger is the same -- failing validation.
>> I tried to reproduce Nick's oops on 5.2-rc but haven't been able to
>> (but I'm not confident I produced the right trigger conditions. will
>> try 5.1).
> OK, I think I found something that triggers this fault.  This happens
> when certain local users try to stat a file or directory on an nfs
> mount.  Presumably these UIDs do not have appropriate permissions on
> the server but I'm not sure exactly (I do not control the server).
> I can reproduce the oops with a command like this:
>   # su -s/bin/sh -c 'stat /path/to/nfs/file' problematic_user
> which oopes every time (and SIGKILLs the stat command).   (I have not yet
> rebooted since the original report or tried with Trond's patch applied.
> I will do that next, and also try 5.1.6).

OK, armed with this reproducer I can confirm that the issue is still
present in 5.1.6, and that applying Trond's patch on top of 5.1.6
appears to fix the problem.


      reply	other threads:[~2019-06-03 18:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-29 15:10 Nick Bowler
2019-05-29 17:13 ` Trond Myklebust
2019-05-29 18:54   ` Olga Kornievskaia
2019-06-03 16:34     ` Nick Bowler
2019-06-03 18:09       ` Nick Bowler [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \
    --subject='Re: PROBLEM: oops spew with Linux 5.1.5 (NFS regression?)' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).