linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: "Venkateswararao Jujjuri (JV)" <jvrao@linux.vnet.ibm.com>
Cc: v9fs-developer@lists.sourceforge.net, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] [fs/9p] Fix NULL point deref in v9fs_dir_release
Date: Tue, 17 Aug 2010 13:13:31 -0400	[thread overview]
Message-ID: <20100817171331.GA26467@infradead.org> (raw)
In-Reply-To: <1282065541-3775-1-git-send-email-jvrao@linux.vnet.ibm.com>

On Tue, Aug 17, 2010 at 10:19:01AM -0700, Venkateswararao Jujjuri (JV) wrote:
> There are situations in VFS where we endup calling v9fs_dir_release() before
> even we instantiate the filp. Hence the check.

Err, what callchain would that be?  This really should not happen.


  reply	other threads:[~2010-08-17 17:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-17 17:19 [PATCH] [fs/9p] Fix NULL point deref in v9fs_dir_release Venkateswararao Jujjuri (JV)
2010-08-17 17:13 ` Christoph Hellwig [this message]
2010-08-17 18:37   ` Venkateswararao Jujjuri (JV)

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=20100817171331.GA26467@infradead.org \
    --to=hch@infradead.org \
    --cc=jvrao@linux.vnet.ibm.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=v9fs-developer@lists.sourceforge.net \
    /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;
as well as URLs for NNTP newsgroup(s).