From: Vivek Goyal <vgoyal@redhat.com>
To: Eric Paris <eparis@parisplace.org>
Cc: WANG Cong <xiyou.wangcong@gmail.com>,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
Eric Paris <eparis@redhat.com>,
"Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: [PATCH] kexec: include sysctl to disable
Date: Thu, 27 Jan 2011 13:50:21 -0500 [thread overview]
Message-ID: <20110127185021.GE23047@redhat.com> (raw)
In-Reply-To: <AANLkTi=LJWvT5r=0rSBxV4aQdm6n2YAS_0y0RkKdTXQp@mail.gmail.com>
On Thu, Jan 27, 2011 at 01:40:02PM -0500, Eric Paris wrote:
> Ping, not hearing any argument is usually a good thing :)
>
So if we allowing locking down module loading, why not allow locking down
kexec kernel loading, hence...
Acked-by: Vivek Goyal <vgoyal@redhat.com>
Vivek
> -Eric
>
> On Thu, Jan 20, 2011 at 12:32 AM, WANG Cong <xiyou.wangcong@gmail.com> wrote:
>
> >> On Wed, 19 Jan 2011 17:26:30 -0500, Eric Paris wrote:
> >>
> >>> much like /proc/sys/kernel/modules_disable is used to disable module
> >>> loading, /proc/sys/kernel/kexec_disable is used to disable kexec code
> >>> loading. It would still be possible to use kexec -l to load a kernel,
> >>> set the tunable to 1 so the kernel waiting to boot couldn't change, and
> >>> then launch the kernel at a later time (through kexec -e or through a
> >>> crash)
>
> > Acked-by: WANG Cong <xiyou.wangcong@gmail.com>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: Vivek Goyal <vgoyal@redhat.com>
To: Eric Paris <eparis@parisplace.org>
Cc: WANG Cong <xiyou.wangcong@gmail.com>,
Eric Paris <eparis@redhat.com>,
linux-kernel@vger.kernel.org, kexec@lists.infradead.org,
"Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: [PATCH] kexec: include sysctl to disable
Date: Thu, 27 Jan 2011 13:50:21 -0500 [thread overview]
Message-ID: <20110127185021.GE23047@redhat.com> (raw)
In-Reply-To: <AANLkTi=LJWvT5r=0rSBxV4aQdm6n2YAS_0y0RkKdTXQp@mail.gmail.com>
On Thu, Jan 27, 2011 at 01:40:02PM -0500, Eric Paris wrote:
> Ping, not hearing any argument is usually a good thing :)
>
So if we allowing locking down module loading, why not allow locking down
kexec kernel loading, hence...
Acked-by: Vivek Goyal <vgoyal@redhat.com>
Vivek
> -Eric
>
> On Thu, Jan 20, 2011 at 12:32 AM, WANG Cong <xiyou.wangcong@gmail.com> wrote:
>
> >> On Wed, 19 Jan 2011 17:26:30 -0500, Eric Paris wrote:
> >>
> >>> much like /proc/sys/kernel/modules_disable is used to disable module
> >>> loading, /proc/sys/kernel/kexec_disable is used to disable kexec code
> >>> loading. It would still be possible to use kexec -l to load a kernel,
> >>> set the tunable to 1 so the kernel waiting to boot couldn't change, and
> >>> then launch the kernel at a later time (through kexec -e or through a
> >>> crash)
>
> > Acked-by: WANG Cong <xiyou.wangcong@gmail.com>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2011-01-27 18:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-19 22:26 [PATCH] kexec: include sysctl to disable Eric Paris
2011-01-19 22:26 ` Eric Paris
2011-01-20 5:21 ` WANG Cong
2011-01-20 5:21 ` WANG Cong
2011-01-20 5:32 ` WANG Cong
2011-01-20 5:32 ` WANG Cong
2011-01-27 18:40 ` Eric Paris
2011-01-27 18:40 ` Eric Paris
2011-01-27 18:50 ` Vivek Goyal [this message]
2011-01-27 18:50 ` Vivek Goyal
2011-01-27 18:56 ` Neil Horman
2011-01-27 18:56 ` Neil Horman
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=20110127185021.GE23047@redhat.com \
--to=vgoyal@redhat.com \
--cc=ebiederm@xmission.com \
--cc=eparis@parisplace.org \
--cc=eparis@redhat.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xiyou.wangcong@gmail.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.