From: Greg KH <gregkh@linuxfoundation.org>
To: Mukesh Ojha <quic_mojha@quicinc.com>
Cc: johannes@sipsolutions.net, rafael@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] devcoredump: Send uevent once devcd is ready
Date: Mon, 6 Nov 2023 20:36:25 +0100 [thread overview]
Message-ID: <2023110659-december-cranium-c98e@gregkh> (raw)
In-Reply-To: <1699280735-31482-1-git-send-email-quic_mojha@quicinc.com>
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
next prev parent reply other threads:[~2023-11-06 19:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-06 14:25 Mukesh Ojha
2023-11-06 19:36 ` Greg KH [this message]
2023-11-06 19:37 ` Johannes Berg
2023-11-07 11:01 ` Mukesh Ojha
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2023110659-december-cranium-c98e@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_mojha@quicinc.com \
--cc=rafael@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®