public inbox for kexec@lists.infradead.org
 help / color / mirror / Atom feed
From: Leizhen (ThunderTown) <thunder.leizhen@huawei.com>
To: kexec@lists.infradead.org
Subject: [PATCH v21 1/5] kdump: return -ENOENT if required cmdline option does not exist
Date: Tue, 15 Mar 2022 21:32:10 +0800	[thread overview]
Message-ID: <d237a2ae-300c-2c51-d97c-417bdfaa5fda@huawei.com> (raw)
In-Reply-To: <YjCE0Scp2YiEJXBM@MiWiFi-R3L-srv>



On 2022/3/15 20:21, Baoquan He wrote:
> On 03/15/22 at 07:57pm, Baoquan He wrote:
>> On 02/27/22 at 11:07am, Zhen Lei wrote:
>>> The crashkernel=Y,low is an optional command-line option. When it doesn't
>>> exist, kernel will try to allocate minimum required memory below 4G
>>> automatically. Give it a unique error code to distinguish it from other
>>> error scenarios.
>>>
>>> Signed-off-by: Zhen Lei <thunder.leizhen@huawei.com>
>>> ---
>>>  kernel/crash_core.c | 3 +--
>>>  1 file changed, 1 insertion(+), 2 deletions(-)
>>>
>>> diff --git a/kernel/crash_core.c b/kernel/crash_core.c
>>> index 256cf6db573cd09..4d57c03714f4e13 100644
>>> --- a/kernel/crash_core.c
>>> +++ b/kernel/crash_core.c
>>> @@ -243,9 +243,8 @@ static int __init __parse_crashkernel(char *cmdline,
>>>  	*crash_base = 0;
>>>  
>>>  	ck_cmdline = get_last_crashkernel(cmdline, name, suffix);
>>> -
>>>  	if (!ck_cmdline)
>>> -		return -EINVAL;
>>> +		return -ENOENT;
>>
>> Firstly, I am not sure if '-ENOENT' is a right value to return. From the
>> code comment of ENOENT, it's used for file or dir?
>> #define ENOENT           2      /* No such file or directory */

This error code does not return to user mode, so there is no problem.
There are a lot of places in the kernel that are used this way. For example:

int stop_one_cpu(unsigned int cpu, cpu_stop_fn_t fn, void *arg)
{
	if (!cpu_stop_queue_work(cpu, &work))
		return -ENOENT;

>>
>> Secondly, we ever discussed the case including
>>  - no crashkernel=,low is provided;
>>  - messy code is provied, e.g crashkernel=aaaaaabbbb,low
> 
> Checking the 3rd pach, this is handled. Take back my below words,
> continue reviewing.

Yes.

> 
>>
>> The 2nd one is not handled in this patchset. How about taking the
>> handling into another round of patches. This patchset just adds
>> crashkernel=,high purely.
>>
>>>  
>>>  	ck_cmdline += strlen(name);
>>>  
>>> -- 
>>> 2.25.1
>>>
>>
> 
> .
> 

-- 
Regards,
  Zhen Lei


  reply	other threads:[~2022-03-15 13:32 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-27  3:07 [PATCH v21 0/5] support reserving crashkernel above 4G on arm64 kdump Zhen Lei
2022-02-27  3:07 ` [PATCH v21 1/5] kdump: return -ENOENT if required cmdline option does not exist Zhen Lei
2022-03-15 11:57   ` Baoquan He
2022-03-15 12:21     ` Baoquan He
2022-03-15 13:32       ` Leizhen [this message]
2022-03-16  5:17         ` Baoquan He
2022-03-16  5:39   ` Baoquan He
2022-03-16  6:15     ` Leizhen
2022-02-27  3:07 ` [PATCH v21 2/5] arm64: Use insert_resource() to simplify code Zhen Lei
2022-02-27  3:07 ` [PATCH v21 3/5] arm64: kdump: reimplement crashkernel=X Zhen Lei
2022-03-16 12:11   ` Baoquan He
2022-03-16 13:11     ` Leizhen
2022-03-17  2:36       ` Baoquan He
2022-03-17  3:19         ` Leizhen
2022-03-17  3:47           ` Baoquan He
2022-03-17  7:30             ` Leizhen
2022-03-17  2:38   ` Baoquan He
2022-03-17  3:23     ` Leizhen
2022-03-21 13:29   ` John Donnelly
2022-03-21 14:09     ` Dave Kleikamp
2022-03-22  1:58     ` Leizhen
2022-02-27  3:07 ` [PATCH v21 4/5] of: fdt: Add memory for devices by DT property "linux, usable-memory-range" Zhen Lei
2022-02-27  3:07 ` [PATCH v21 5/5] docs: kdump: Update the crashkernel description for arm64 Zhen Lei
2022-03-15 11:59   ` Baoquan He
2022-04-08  9:32 ` [PATCH v21 0/5] support reserving crashkernel above 4G on arm64 kdump Baoquan He
2022-04-08  9:47   ` Leizhen
2022-04-11  2:56     ` Baoquan He

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=d237a2ae-300c-2c51-d97c-417bdfaa5fda@huawei.com \
    --to=thunder.leizhen@huawei.com \
    --cc=kexec@lists.infradead.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