mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
	Trond Myklebust <Trond.Myklebust@netapp.com>
Subject: Re: [GIT PULL] fuse fix for 2.6.39
Date: Thu, 12 May 2011 08:12:24 -0700	[thread overview]
Message-ID: <BANLkTin6Ujea+qdkvwkH_9o5F8WKPyFdyA@mail.gmail.com> (raw)
In-Reply-To: <87fwokarjj.fsf@tucsk.pomaz.szeredi.hu>

Hmm.

Do we really ever have a NULL 'nd' these days? Can you send me the
backtrace for whatever oops that was reported?

The reason I ask is because at least NFS also does just

        if (nd->flags & LOOKUP_RCU)
                return -ECHILD;

in its nfs_lookup/open_revalidate() functions. As does cifs, ncpfs, p9
and coda from a quick grep.

                        Linus

On Thu, May 12, 2011 at 8:04 AM, Miklos Szeredi <miklos@szeredi.hu> wrote:
>
> Please pull from
>
>  git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git for-linus
>
> Miklos Szeredi (1):
>      fuse: fix oops in revalidate when called with NULL nameidata
>
> ---
>  fs/fuse/dir.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
>

  reply	other threads:[~2011-05-12 15:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-12 15:04 Miklos Szeredi
2011-05-12 15:12 ` Linus Torvalds [this message]
2011-05-12 15:19   ` Linus Torvalds
2011-05-12 16:28     ` Trond Myklebust
2011-05-12 17:21       ` Linus Torvalds
2011-05-12 17:40         ` Al Viro
2011-05-12 18:52           ` Trond Myklebust
2011-05-12 17:46         ` Trond Myklebust
2011-05-12 18:01           ` Linus Torvalds

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=BANLkTin6Ujea+qdkvwkH_9o5F8WKPyFdyA@mail.gmail.com \
    --to=torvalds@linux-foundation.org \
    --cc=Trond.Myklebust@netapp.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®