mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kumar Gala <galak@kernel.crashing.org>
To: Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	nfs@lists.sourceforge.net, neilb@suse.de, bfields@fieldses.org,
	chuck.lever@oracle.com
Subject: Re: LTP ustat01 test fails on NFSROOT
Date: Fri, 26 Oct 2007 04:42:28 -0500	[thread overview]
Message-ID: <0CC518FE-47B0-4A32-B682-1CA5F7CBAC2F@kernel.crashing.org> (raw)
In-Reply-To: <1193335168.7705.39.camel@heimdal.trondhjem.org>


On Oct 25, 2007, at 12:59 PM, Trond Myklebust wrote:

> Could you please try the following patch?
>
> Cheers
>   Trond
> --------------------------------- CUT HERE  
> -----------------------------
> From: Trond Myklebust <Trond.Myklebust@netapp.com>
> Date: Thu, 25 Oct 2007 13:56:10 -0400
> NFS: Fix the ustat() regression
>
> Since 2.6.18, the superblock sb->s_root has been a dummy dentry with a
> dummy inode. This breaks ustat(), which actually uses sb->s_root in a
> vfstat() call.
>
> Fix this by making the s_root a dummy alias to the directory inode  
> that was
> used when creating the superblock.
>
> Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
> ---
>
>  fs/nfs/getroot.c |   81 +++++++++++++++++ 
> +------------------------------------
>  1 files changed, 27 insertions(+), 54 deletions(-)

Any reason not to send this to Linus as a bug fix for 2.6.24 (and  
possibly stable)?

- k

  parent reply	other threads:[~2007-10-26  9:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-23 22:52 Kumar Gala
2007-10-24  1:21 ` Trond Myklebust
2007-10-24  5:05   ` Kumar Gala
2007-10-25 15:59     ` Kumar Gala
2007-10-25 17:59       ` Trond Myklebust
2007-10-25 18:36         ` Kumar Gala
2007-10-25 18:39           ` Trond Myklebust
2007-10-25 19:05             ` Kumar Gala
2007-10-26  9:42         ` Kumar Gala [this message]
2007-10-29 14:41           ` Kumar Gala
2007-11-02 14:28         ` Kumar Gala
2007-11-08  7:36           ` Kumar Gala

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=0CC518FE-47B0-4A32-B682-1CA5F7CBAC2F@kernel.crashing.org \
    --to=galak@kernel.crashing.org \
    --cc=Trond.Myklebust@netapp.com \
    --cc=bfields@fieldses.org \
    --cc=chuck.lever@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=nfs@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

all inboxes | Powered by JetHome®