[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160715130955.GC23514@redhat.com>
Date: Fri, 15 Jul 2016 09:09:55 -0400
From: Vivek Goyal <vgoyal@...hat.com>
To: AKASHI Takahiro <takahiro.akashi@...aro.org>
Cc: ebiederm@...ssion.com, dyoung@...hat.com, bhe@...hat.com,
bauerman@...ux.vnet.ibm.com, arnd@...db.de,
kexec@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linuxppc-dev@...ts.ozlabs.org
Subject: Re: [RFC 3/3] kexec: extend kexec_file_load system call
On Tue, Jul 12, 2016 at 10:42:01AM +0900, AKASHI Takahiro wrote:
[..]
> -SYSCALL_DEFINE5(kexec_file_load, int, kernel_fd, int, initrd_fd,
> +SYSCALL_DEFINE6(kexec_file_load, int, kernel_fd, int, initrd_fd,
> unsigned long, cmdline_len, const char __user *, cmdline_ptr,
> - unsigned long, flags)
> + unsigned long, flags, const struct kexec_fdset __user *, ufdset)
Can one add more parameters to existing syscall. Can it break existing
programs with new kernel? I was of the impression that one can't do that.
But may be I am missing something.
Vivek
Powered by blists - more mailing lists