From: Ananth N Mavinakayanahalli <ananth@linux.ibm.com>
To: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v2] powernv/elog: Fix the race while processing OPAL error log event.
Date: Mon, 5 Oct 2020 16:17:14 +0530 [thread overview]
Message-ID: <df7cebd0-bec3-d716-5514-61c4043a6d30@linux.ibm.com> (raw)
In-Reply-To: <160187115555.1589942.2124270585910076829.stgit@jupiter>
On 10/5/20 9:42 AM, Mahesh Salgaonkar wrote:
> Every error log reported by OPAL is exported to userspace through a sysfs
> interface and notified using kobject_uevent(). The userspace daemon
> (opal_errd) then reads the error log and acknowledges it error log is saved
> safely to disk. Once acknowledged the kernel removes the respective sysfs
> file entry causing respective resources getting released including kobject.
>
> However there are chances where user daemon may already be scanning elog
> entries while new sysfs elog entry is being created by kernel. User daemon
> may read this new entry and ack it even before kernel can notify userspace
> about it through kobject_uevent() call. If that happens then we have a
> potential race between elog_ack_store->kobject_put() and kobject_uevent
> which can lead to use-after-free issue of a kernfs object resulting into a
> kernel crash. This patch fixes this race by protecting a sysfs file
> creation/notification by holding an additional reference count on kobject
> until we safely send kobject_uevent().
>
> Reported-by: Oliver O'Halloran <oohall@gmail.com>
> Signed-off-by: Mahesh Salgaonkar <mahesh@linux.ibm.com>
> Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.ibm.com>
cc stable?
--
Ananth
next prev parent reply other threads:[~2020-10-05 12:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-05 4:12 [PATCH v2] powernv/elog: Fix the race while processing OPAL error log event Mahesh Salgaonkar
2020-10-05 10:47 ` Ananth N Mavinakayanahalli [this message]
2020-10-06 0:22 ` Oliver O'Halloran
2020-10-06 5:11 ` Mahesh Jagannath Salgaonkar
2020-10-06 0:25 ` Oliver O'Halloran
2020-10-06 2:26 ` Vasant Hegde
2020-10-06 4:48 ` Mahesh Jagannath Salgaonkar
2020-10-06 5:40 ` Michael Ellerman
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=df7cebd0-bec3-d716-5514-61c4043a6d30@linux.ibm.com \
--to=ananth@linux.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).