[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200702131430.47053.agruen@suse.de>
Date: Tue, 13 Feb 2007 14:30:46 -0800
From: Andreas Gruenbacher <agruen@...e.de>
To: Greg KH <greg@...ah.com>
Cc: torvalds@...ux-foundation.org, neilb@...e.de,
viro@...iv.linux.org.uk, hch@....de, akpm@...ux-foundation.org,
linux-kernel@...r.kernel.org
Subject: Re: Bug in current -git tree causing dbus and gnome to chew up cpu time
On Tuesday 13 February 2007 13:37, Greg KH wrote:
> On Tue, Feb 13, 2007 at 11:58:02AM -0800, Andreas Gruenbacher wrote:
> > > I'm running pretty new GNOME and dbus here:
> > > dbus 1.0.2
> > > gnome 2.16.2
> > > hal 0.5.7.1
> > > nautilus 2.16.3
> > >
> > > Any ideas of things I can test?
> >
> > Sorry for the breakage. Printk of the __d_path result may tell:
> >
> > Index: b/fs/dcache.c
> > ===================================================================
> > --- a/fs/dcache.c
> > +++ b/fs/dcache.c
> > @@ -1803,6 +1803,8 @@ char *__d_path(struct dentry *dentry, st
> >
> > out:
> > spin_unlock(&dcache_lock);
> > + printk(KERN_DEBUG "%s(%d): %s\n", current->comm, current->pid,
> > + IS_ERR(buffer) ? "failed" : buffer);
> > return buffer;
>
> This causes the following to just loop over and over, incrementing the
> pid:
>
> gnome-vfs-daemo(8914):
That's the weird case, and it should only trigger if there's no path to be
recovered from what gnome-vfs-deamon calls d_path on, like a lazily unmounted
filesystem. (A bind mount wouldn't do.)
> I'm running gnome-vfs version 2.6.13 if that matters.
>
> Anything else I can try?
I guess I'll just have to check what gnome-vfs-deamon does, thanks.
Andreas
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists