From: Greg KH <greg@kroah.com>
To: Alessandro Suardi <alessandro.suardi@gmail.com>
Cc: Andreas Gruenbacher <agruen@suse.de>,
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: Wed, 14 Feb 2007 08:39:48 -0800 [thread overview]
Message-ID: <20070214163948.GA5846@kroah.com> (raw)
In-Reply-To: <5a4c581d0702140313q6d048eufa83d7b3d058311@mail.gmail.com>
On Wed, Feb 14, 2007 at 12:13:52PM +0100, Alessandro Suardi wrote:
> On 2/14/07, Andreas Gruenbacher <agruen@suse.de> wrote:
> >Hi,
> >
> >I've described the problem and possible fixes in the "Re: [PATCH] Fix
> >d_path
> >for lazy unmounts" thread, Message-Id: 200702140019.36378.agruen@suse.de.
>
> Yes, I saw that. But there isn't any patch for me to test, and my
> userspace remains broken. Please don't get me wrong - I'm
> not bitching about this, but I will effectively not be able to test
> newer snapshots until either a fix for this new bug gets in, or
> the commit that introduced the bug gets reverted.
The commit was reverted, the latest git tree should work just fine.
thanks,
greg k-h
prev parent reply other threads:[~2007-02-14 16:41 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
[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 [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=20070214163948.GA5846@kroah.com \
--to=greg@kroah.com \
--cc=agruen@suse.de \
--cc=akpm@linux-foundation.org \
--cc=alessandro.suardi@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.