linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Van Hensbergen <ericvh@gmail.com>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: oddity in v9fs_kill_super()
Date: Mon, 11 May 2009 13:55:57 -0500	[thread overview]
Message-ID: <a4e6962a0905111155h4b575a70o8453938e53b88e3d@mail.gmail.com> (raw)
In-Reply-To: <20090506175906.GW8633@ZenIV.linux.org.uk>

On Wed, May 6, 2009 at 12:59 PM, Al Viro <viro@zeniv.linux.org.uk> wrote:
> Is there any reason to do v9fs_dentry_release(s->s_root) in ->kill_sb()?
> It is called when root dentry is freed and it will be freed just fine...
>

Most likely unnecessary early paranoia on my part - I think that's
been in there since 2.6.14.
I'll look into removing it.

        -eric

      reply	other threads:[~2009-05-11 18:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-06 17:59 oddity in v9fs_kill_super() Al Viro
2009-05-11 18:55 ` Eric Van Hensbergen [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:
  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=a4e6962a0905111155h4b575a70o8453938e53b88e3d@mail.gmail.com \
    --to=ericvh@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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).