From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Hari Bathini <hbathini@linux.ibm.com>
Cc: linuxppc-dev <linuxppc-dev@ozlabs.org>,
Dave Young <dyoung@redhat.com>,
Mahesh J Salgaonkar <mahesh@linux.ibm.com>,
Petr Tesarik <ptesarik@suse.cz>
Subject: Re: powerpc/fadump: re-register firmware-assisted dump if already registered
Date: Thu, 20 Sep 2018 14:21:06 +1000 (AEST) [thread overview]
Message-ID: <42G3Sf1sg4z9sCS@ozlabs.org> (raw)
In-Reply-To: <153693396241.22873.15797641996113409474.stgit@hbathini.in.ibm.com>
On Fri, 2018-09-14 at 14:06:02 UTC, Hari Bathini wrote:
> Firmware-Assisted Dump (FADump) needs to be registered again after any
> memory hot add/remove operation to update the crash memory ranges. But
> currently, the kernel returns '-EEXIST' if we try to register without
> uregistering it first. This could expose the system to racing issues
> while unregistering and registering FADump from userspace during udev
> events. Spare the userspace of this and let it be taken care of in the
> kernel space for a simpler interface.
>
> Since this change, running 'echo 1 > /sys/kernel/fadump_registered'
> would result in re-regisering (unregistering and registering) FADump,
> if it was already registered.
>
> Signed-off-by: Hari Bathini <hbathini@linux.ibm.com>
> Acked-by: Mahesh Salgaonkar <mahesh@linux.vnet.ibm.com>
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/0823c68b054bca9dc321adea829af5
cheers
prev parent reply other threads:[~2018-09-20 4:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-14 14:06 [PATCH] powerpc/fadump: re-register firmware-assisted dump if already registered Hari Bathini
2018-09-14 14:28 ` Petr Tesarik
2018-09-14 15:38 ` Hari Bathini
2018-09-18 16:46 ` Mahesh Jagannath Salgaonkar
2018-09-20 4:21 ` Michael Ellerman [this message]
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=42G3Sf1sg4z9sCS@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=dyoung@redhat.com \
--cc=hbathini@linux.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=mahesh@linux.ibm.com \
--cc=ptesarik@suse.cz \
/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).