| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <3ae72650705100833h35dbc5fer7553529d643c742c@mail.gmail.com> Date: Thu, 10 May 2007 17:33:27 +0200 From: "Kay Sievers" <kay.sievers@...y.org> To: "Tejun Heo" <htejun@...il.com> Cc: "Greg KH" <greg@...ah.com>, "Chris Rankin" <rankincj@...oo.com>, "Alan Stern" <stern@...land.harvard.edu>, linux-usb-devel@...ts.sourceforge.net, linux-kernel <linux-kernel@...r.kernel.org>, stable@...nel.org Subject: Re: [PATCH] driver-core: don't free devt_attr till the device is released On 5/10/07, Tejun Heo <htejun@...il.com> wrote: > Currently, devt_attr for the "dev" file is freed immediately on device > removal, but if the "dev" sysfs file is open when a device is removed, > sysfs will access its attribute structure for further access including > close resulting in jumping to garbled address. Fix it by postponing > freeing devt_attr to device release time. > > Note that devt_attr for class_device is already freed on release. Hi Tejun, your rework removes the "owner" field from the attributes. I think we kept the "dev" and "uevent" attribute as part of "struct device" only to be able to assign it the actual owner of the module that has created the device. The attribute can probably just live as one instance statically in the driver core now? Thanks, Kay - 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