From: Michael Ellerman <mpe@ellerman.id.au>
To: Mahesh Jagannath Salgaonkar <mahesh@linux.vnet.ibm.com>,
Michal Suchanek <msuchanek@suse.de>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
Hari Bathini <hbathini@linux.vnet.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Colin Ian King <colin.king@canonical.com>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] powerpc/fadump: return error when fadump registration fails
Date: Tue, 30 May 2017 20:45:13 +1000 [thread overview]
Message-ID: <87bmqa62ti.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <e1caa0a3-50a0-aff3-3687-2ef31841e587@linux.vnet.ibm.com>
Mahesh Jagannath Salgaonkar <mahesh@linux.vnet.ibm.com> writes:
> On 05/27/2017 09:16 PM, Michal Suchanek wrote:
>> - log an error message when registration fails and no error code listed
>> in the switch is returned
>> - translate the hv error code to posix error code and return it from
>> fw_register
>> - return the posix error code from fw_register to the process writing
>> to sysfs
>> - return EEXIST on re-registration
>> - return success on deregistration when fadump is not registered
>> - return ENODEV when no memory is reserved for fadump
>
> Why do we need this ?
Because that's how we do error handling.
> Userspace can always read back the fadump registration status from
> /sys/kernel/fadump_registered (after echo 1 to it) to find out
> whether fadump registration succeeded or not.
That's a terrible API.
If we followed that example, open() wouldn't return a value, you'd have
to do another syscall to check if it worked.
I'd appreciate if someone could test this and give me a Tested-by.
cheers
next prev parent reply other threads:[~2017-05-30 10:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-27 15:46 Michal Suchanek
2017-05-30 4:41 ` Mahesh Jagannath Salgaonkar
2017-05-30 10:45 ` Michael Ellerman [this message]
2017-06-01 10:00 ` Hari Bathini
2017-06-05 10:21 ` [v2] " 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=87bmqa62ti.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=colin.king@canonical.com \
--cc=hbathini@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mahesh@linux.vnet.ibm.com \
--cc=msuchanek@suse.de \
--cc=paulus@samba.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®