On Fri, Sep 05, 2014 at 08:51:58PM +0800, Baoquan He wrote:
On 09/05/14 at 07:53am, Vivek Goyal wrote:
> On Fri, Sep 05, 2014 at 10:57:31AM +0800, Baoquan He wrote:
> > On 09/05/14 at 10:45am, Dave Young wrote:
> > > On 09/05/14 at 10:16am, Dave Young wrote:
> > > > On 09/03/14 at 12:07pm, Vivek Goyal wrote:
> > > > > Currently old kexec syscall denies unloading a kernel if
secureboot is enabled.
> > > > > I think this is not right behavior and should be changed. But
for now, use
> > > > > new syscall if secureboot is enabled and that allows unloading
kernel.
> > > >
> > > > We need to make sure the new syscall is in latest Fedora kernel, then
we can add
> > > > this patch in kexec-tools.
> > >
> > > BTW, seems there's a new kconfig option for the syscall, it need a
fedora kernel
> > > patch if it's not default on.
> >
> > Yeah, I was a little surprised when the OS said kexec_file_load is not
> > implemented yet. Is there any concern about defaulting CONFIG_KEXEC_FILE
> > now?
>
> I think it is perfectly fine. This kexec-tools should be able to run
> on kernels which have CONFIG_KEXEC_FILE=n and user space should display
> correct error message.
Yes, understood it after discussion with Dave. Just a little confusing
when found kexec_file_load suddenly didn't work. I even used gdb to
check it. That will be better if user space can tell the reason more
clearly.
Btw, this will be opened in rhel and fedora, right?
Yes. Latest fedora kernels have already enabled it. I will post RHEL
patches pretty soon.
Thanks
Vivek