[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20071214172814.GA14597@suse.de>
Date: Fri, 14 Dec 2007 09:28:14 -0800
From: Greg KH <gregkh@...e.de>
To: Dhaval Giani <dhaval@...ux.vnet.ibm.com>
Cc: Ingo Molnar <mingo@...e.hu>, Kay Sievers <kay.sievers@...y.org>,
vincent.fortier1@...gc.ca, Randy Dunlap <randy.dunlap@...cle.com>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org,
Srivatsa Vaddagiri <vatsa@...ux.vnet.ibm.com>,
Balbir Singh <balbir@...ibm.com>, maneesh@...ibm.com
Subject: Re: 2.6.22.14 oops msg with commvault galaxy ?
On Fri, Dec 14, 2007 at 10:37:39PM +0530, Dhaval Giani wrote:
> On Fri, Dec 14, 2007 at 08:26:42AM -0800, Greg KH wrote:
> > On Thu, Dec 13, 2007 at 09:21:26PM +0100, Ingo Molnar wrote:
> > >
> > > * Kay Sievers <kay.sievers@...y.org> wrote:
> > >
> > > > > > > This one also fails to apply properly at the exact same place
> > > > > > > has Ingo's previously posted patch. Would need to backport his
> > > > > > > one.
> > > > > >
> > > > > > It depends on a completely reworked sysfs logic, I don't think it
> > > > > > makes any sense to backport that.
> > > > >
> > > > > well, if it fixes a live bug in a still supported stable kernel
> > > > > release...
> > > > >
> > > > > Vincent, could you try to just get rid of all actual uses of
> > > > > se->attr.owner, within fs/sysfs/*.c? Something like the patch below.
> > > > > (totally untested - might be fatally broken as well)
> > > >
> > > > How can you think that this is not needed? You can not remove it with
> > > > sysfs you are patching. Hope this explains it:
> > > > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=0ab66088c855eca68513bdd7442a426c4b374ced
> > >
> > > yeah - as i said it might be fatally broken (in fact it is). Do we
> > > understand why Vincent got the crashes with vanilla 2.6.22.14 ?
> >
> > No, and I can't seem to duplicate them here at all.
> >
> > Does anyone have a test case for this that I can work on trying to
> > duplicate?
> >
>
> If you apply CFS without my fix, and try to constantly check cpu_shares
> for a user who is logging and logging out, you should hit it. (That's
> what I was doing).
Hm, how about a "vanilla 2.6.22.14 kernel _without_ any patches".
That's what I am most worried about :)
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