[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20071213125509.GA28340@elte.hu>
Date: Thu, 13 Dec 2007 13:55:09 +0100
From: Ingo Molnar <mingo@...e.hu>
To: Dhaval Giani <dhaval@...ux.vnet.ibm.com>
Cc: "Fortier,Vincent [Montreal]" <Vincent.Fortier1@...GC.CA>,
Greg KH <gregkh@...e.de>,
Randy Dunlap <randy.dunlap@...cle.com>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org,
Srivatsa Vaddagiri <vatsa@...ux.vnet.ibm.com>,
kay.sievers@...y.org, Balbir Singh <balbir@...ibm.com>,
maneesh@...ibm.com
Subject: Re: 2.6.22.14 oops msg with commvault galaxy ?
* Dhaval Giani <dhaval@...ux.vnet.ibm.com> wrote:
> Could you please see if the following patch removes the oops due to
> CFS sysfs files? (There might still be the other oops due to the
> floppy sysfs files)
>
> Ingo, could you please add this patch in your CFS backport to 2.6.22
> and older kernels?
sure - i've updated the backport patches with this fix.
> static void user_attr_init(struct subsys_attribute *sa, char *name, int mode)
> {
> + sa->attr.owner = NULL;
> sa->attr.name = name;
i'm wondering why doesnt this affect 2.6.23 and later? Does sysfs
initialize the owner field to NULL automatically?
Ingo
--
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