From: Andreas Gruenbacher <agruen@suse.de>
To: Greg KH <greg@kroah.com>
Cc: torvalds@linux-foundation.org, neilb@suse.de,
viro@zeniv.linux.org.uk, hch@lst.de, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: Bug in current -git tree causing dbus and gnome to chew up cpu time
Date: Tue, 13 Feb 2007 11:58:02 -0800 [thread overview]
Message-ID: <200702131158.02809.agruen@suse.de> (raw)
In-Reply-To: <20070213195116.GA5181@kroah.com>
On Tuesday 13 February 2007 11:51, Greg KH wrote:
> Hi,
>
> I've used 'git bisect' to track down a change in the latest git tree
> that is causing dbus-daemon to sit and spin at the time GNOME launches,
> preventing nautlius from ever running.
>
> The bad commit is:
> commit eb3dfb0cb1f4a44e2d0553f89514ce9f2a9fcaf1
> Author: Andreas Gruenbacher <agruen@suse.de>
> Date: Mon Feb 12 00:51:47 2007 -0800
>
> [PATCH] Fix d_path for lazy unmounts
>
> With that patch out, GNOME startup works just fine. I have a strace of
> the dbus process running showing the problem, if anyone thinks that will
> help out any.
I'd like to see that, please.
> 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;
global_root:
Thanks,
Andreas
next prev parent reply other threads:[~2007-02-13 19:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-13 19:51 Bug in current -git tree causing dbus and gnome to chew up cpu time Greg KH
2007-02-13 19:58 ` Andreas Gruenbacher [this message]
[not found] ` <20070213200132.GA6149@kroah.com>
2007-02-13 20:16 ` Andreas Gruenbacher
2007-02-13 21:37 ` Greg KH
2007-02-13 22:30 ` Andreas Gruenbacher
2007-02-13 22:39 ` Neil Brown
2007-02-13 23:03 ` Andreas Gruenbacher
2007-02-14 9:47 ` Alessandro Suardi
2007-02-14 9:57 ` Andreas Gruenbacher
2007-02-14 11:13 ` Alessandro Suardi
2007-02-14 16:39 ` Greg KH
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=200702131158.02809.agruen@suse.de \
--to=agruen@suse.de \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
--cc=torvalds@linux-foundation.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