Messages in this thread | | | Date | Mon, 6 Nov 2023 20:36:25 +0100 | From | Greg KH <> | Subject | Re: [PATCH] devcoredump: Send uevent once devcd is ready |
| |
On Mon, Nov 06, 2023 at 07:55:35PM +0530, Mukesh Ojha wrote: > dev_coredumpm() creates a devcoredump device and adds it > to the core kernel framework which eventually end up > sending uevent to the user space and later creates a > symbolic link to the failed device. An application > running in userspace may be interested in this symbolic > link to get the name of the failed device. > > In a issue scenario, once uevent sent to the user space > it start reading '/sys/class/devcoredump/devcdX/failing_device' > to get the actual name of the device which might not been > created and it is in its path of creation. > > To fix this, suppress sending uevent till the failing device > symbolic link gets created and send uevent once symbolic > link is created successfully. > > Signed-off-by: Mukesh Ojha <quic_mojha@quicinc.com>
What commit id does this fix? What in-kernel driver does this affect that is using devcoredump?
thanks,
greg k-h
| |