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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <5213ABB9.5060600@linux.intel.com>
Date:	Tue, 20 Aug 2013 10:47:37 -0700
From:	Srinivas Pandruvada <srinivas.pandruvada@...ux.intel.com>
To:	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: kobject_uevent call in device_add

Is there any specific reason that "kobject_uevent(&dev->kobj, KOBJ_ADD)
is called before calling  "class_intf->add_dev(dev, class_intf) in the 
function device_add()?

I am wondering if we call after class_intf->add_dev, it will provide 
opportunity for
client drivers to do some operation before user space is notified.

Thanks,
Srinivas





--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ