All of lore.kernel.org
 help / color / mirror / Atom feed
From: Baoquan He <bhe@redhat.com>
To: "Lee, Chun-Yi" <joeyli.kernel@gmail.com>
Cc: "Lee, Chun-Yi" <jlee@suse.com>, Simon Horman <horms@verge.net.au>,
	kexec@lists.infradead.org, Vivek Goyal <vgoyal@redhat.com>,
	Petr Tesarik <ptesarik@suse.com>
Subject: Re: [PATCH] kexec: Add option to fallback to old kexec syscall when kexec file based syscall failed
Date: Thu, 14 Jul 2016 17:51:24 +0800	[thread overview]
Message-ID: <20160714095124.GA9366@x1.redhat.com> (raw)
In-Reply-To: <1468485911-21427-1-git-send-email-jlee@suse.com>

On 07/14/16 at 04:45pm, Lee, Chun-Yi wrote:
> This patch adds a new "--fallback-kexec" option to give a chance to
> fallback to old kexec syscall when file based kexec syscall operation
> failed.
> 
> This option works with --kexec-file-syscall to provide more flexible
> way to adapt to different kernels that those kernels built with
> different kexec syscall config or have different verification policy.

Usually distribuition system uses script to build a framework to
connect the kexec/kdump, makedumpfile utility chain. This can make user
execute a very simple script command to implement kexec load or kexec
jumping job. In this case script can do what you are trying to do.

Besides, have you actually met that kexec-file failed but old kexec
syscall works? I mean how did you test it? I am wondering when it will
happen.

Thanks
Baoquan

> 
> Cc: Simon Horman <horms@verge.net.au>
> Cc: Petr Tesarik <ptesarik@suse.com>
> Cc: Vivek Goyal <vgoyal@redhat.com>
> Signed-off-by: Lee, Chun-Yi <jlee@suse.com>
> ---
>  kexec/kexec.c | 13 +++++++++++++
>  kexec/kexec.h |  4 +++-
>  2 files changed, 16 insertions(+), 1 deletion(-)
> 
> diff --git a/kexec/kexec.c b/kexec/kexec.c
> index 500e5a9..e05b43f 100644
> --- a/kexec/kexec.c
> +++ b/kexec/kexec.c
> @@ -969,6 +969,7 @@ void usage(void)
>  	       "                      preserve context)\n"
>  	       "                      to original kernel.\n"
>  	       " -s, --kexec-file-syscall Use file based syscall for kexec operation\n"
> +	       "     --fallback-kexec     Fallback to old kexec when file based syscall failed\n"
>  	       " -d, --debug           Enable debugging to help spot a failure.\n"
>  	       "\n"
>  	       "Supported kernel file types and options: \n");
> @@ -1204,6 +1205,7 @@ int main(int argc, char *argv[])
>  	int do_unload = 0;
>  	int do_reuse_initrd = 0;
>  	int do_kexec_file_syscall = 0;
> +	int do_fallback_kexec_syscall = 0;
>  	void *entry = 0;
>  	char *type = 0;
>  	char *endptr;
> @@ -1226,9 +1228,13 @@ int main(int argc, char *argv[])
>  		case OPT_KEXEC_FILE_SYSCALL:
>  			do_kexec_file_syscall = 1;
>  			break;
> +		case OPT_FALLBACK_KEXEC:
> +			do_fallback_kexec_syscall = 1;
> +			break;
>  		}
>  	}
>  
> +fallback:
>  	/* Reset getopt for the next pass. */
>  	opterr = 1;
>  	optind = 1;
> @@ -1407,6 +1413,13 @@ int main(int argc, char *argv[])
>  			result = my_load(type, fileind, argc, argv,
>  						kexec_flags, entry);
>  	}
> +	/* fallback to old kexec syscall */
> +	if (do_kexec_file_syscall && result != 0 && do_fallback_kexec_syscall) {
> +		fprintf(stderr, "Fallback to kexec syscall\n");
> +		do_kexec_file_syscall = 0;
> +		do_fallback_kexec_syscall = 0;
> +		goto fallback;
> +	}
>  	/* Don't shutdown unless there is something to reboot to! */
>  	if ((result == 0) && (do_shutdown || do_exec) && !kexec_loaded()) {
>  		die("Nothing has been loaded!\n");
> diff --git a/kexec/kexec.h b/kexec/kexec.h
> index 9194f1c..65dbd56 100644
> --- a/kexec/kexec.h
> +++ b/kexec/kexec.h
> @@ -225,7 +225,8 @@ extern int file_types;
>  #define OPT_LOAD_PRESERVE_CONTEXT 259
>  #define OPT_LOAD_JUMP_BACK_HELPER 260
>  #define OPT_ENTRY		261
> -#define OPT_MAX			262
> +#define OPT_FALLBACK_KEXEC	262
> +#define OPT_MAX			263
>  #define KEXEC_OPTIONS \
>  	{ "help",		0, 0, OPT_HELP }, \
>  	{ "version",		0, 0, OPT_VERSION }, \
> @@ -244,6 +245,7 @@ extern int file_types;
>  	{ "mem-max",		1, 0, OPT_MEM_MAX }, \
>  	{ "reuseinitrd",	0, 0, OPT_REUSE_INITRD }, \
>  	{ "kexec-file-syscall",	0, 0, OPT_KEXEC_FILE_SYSCALL }, \
> +	{ "fallback-kexec",     0, 0, OPT_FALLBACK_KEXEC }, \
>  	{ "debug",		0, 0, OPT_DEBUG }, \
>  
>  #define KEXEC_OPT_STR "h?vdfxyluet:ps"
> -- 
> 2.6.6
> 
> 
> _______________________________________________
> kexec mailing list
> kexec@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/kexec

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  reply	other threads:[~2016-07-14  9:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-14  8:45 [PATCH] kexec: Add option to fallback to old kexec syscall when kexec file based syscall failed Lee, Chun-Yi
2016-07-14  9:51 ` Baoquan He [this message]
2016-07-14 10:02   ` Baoquan He
2016-07-14 10:35   ` joeyli
2016-07-14 14:12     ` Baoquan He
2016-07-14 14:53 ` Vivek Goyal
2016-07-14 23:57   ` joeyli
2016-07-15  7:58     ` Petr Tesarik
2016-07-15 10:28       ` joeyli
2016-07-15 11:20         ` Petr Tesarik
2016-07-15 12:51       ` Vivek Goyal
2016-07-15 14:42         ` Petr Tesarik
2016-07-15 15:13           ` Vivek Goyal
2016-07-15 15:26             ` Petr Tesarik

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=20160714095124.GA9366@x1.redhat.com \
    --to=bhe@redhat.com \
    --cc=horms@verge.net.au \
    --cc=jlee@suse.com \
    --cc=joeyli.kernel@gmail.com \
    --cc=kexec@lists.infradead.org \
    --cc=ptesarik@suse.com \
    --cc=vgoyal@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.