[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070607160107.GA17800@kroah.com>
Date: Thu, 7 Jun 2007 09:01:07 -0700
From: Greg KH <greg@...ah.com>
To: Jiri Slaby <jirislaby@...il.com>
Cc: Tejun Heo <htejun@...il.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Mikael Pettersson <mikpe@...uu.se>,
linux-kernel@...r.kernel.org
Subject: Re: 2.6.22-rc4-mm1
On Thu, Jun 07, 2007 at 05:54:13PM +0200, Jiri Slaby wrote:
> Tejun Heo napsal(a):
> > Jiri Slaby wrote:
> >> Tejun Heo napsal(a):
> >>> Jiri Slaby wrote:
> >>>> Yes. Now I'm compiling -rc4-mm2.
> >>> It's probably caused by new sysfs slimdown patches and I'm pretty sure
> >>> -rc4-mm2 would fail the same way. The offending one should be one of
> >>> the following patches.
> >> There's reverted gregkh-driver-block-device in -mm2. So I wanted to give it a
> >> try. Do you think it's pointless and that patch has no impact on the behaviour?
> >
> > I'm not familiar with how lvm vgscan works and the patch does look like
> > it can affect that. Please give a shot at -mm2.
>
> Yup, it works without any further patches. So it seems like
> gregkh-driver-block-device is the culprit?
Culprit for what kind of symptom? Is CONFIG_SYSFS_DEPRECATED enabled?
If not, can you try that?
thanks,
greg k-h
-
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