(2014/11/26 4:29), Jiri Kosina wrote:
> On Tue, 25 Nov 2014, Steven Rostedt wrote:
>
>> It is not guaranteed from ftrace's stand point. What happens if we have
>> a kprobe handler that modifies it for someplace else? Changing the ip
>> address may not be a kpatch/kGraft privilege only.
>
> This
(2014/11/26 4:29), Jiri Kosina wrote:
On Tue, 25 Nov 2014, Steven Rostedt wrote:
It is not guaranteed from ftrace's stand point. What happens if we have
a kprobe handler that modifies it for someplace else? Changing the ip
address may not be a kpatch/kGraft privilege only.
This brings me
On Tue, 25 Nov 2014, Steven Rostedt wrote:
> It is not guaranteed from ftrace's stand point. What happens if we have
> a kprobe handler that modifies it for someplace else? Changing the ip
> address may not be a kpatch/kGraft privilege only.
This brings me back to the RFC patch I sent back then
On Tue, 25 Nov 2014 18:04:31 +0100
Petr Mladek wrote:
> On Tue 2014-11-25 11:52:10, Steven Rostedt wrote:
> > On Tue, 25 Nov 2014 17:39:43 +0100
> > Petr Mladek wrote:
> >
> > > On Fri 2014-11-21 11:39:24, Masami Hiramatsu wrote:
> > > > (2014/11/21 7:29), Seth Jennings wrote:
> > > > > This
On Tue 2014-11-25 11:52:10, Steven Rostedt wrote:
> On Tue, 25 Nov 2014 17:39:43 +0100
> Petr Mladek wrote:
>
> > On Fri 2014-11-21 11:39:24, Masami Hiramatsu wrote:
> > > (2014/11/21 7:29), Seth Jennings wrote:
> > > > This commit introduces code for the live patching core. It implements
> > >
On Tue, 25 Nov 2014 17:39:43 +0100
Petr Mladek wrote:
> On Fri 2014-11-21 11:39:24, Masami Hiramatsu wrote:
> > (2014/11/21 7:29), Seth Jennings wrote:
> > > This commit introduces code for the live patching core. It implements
> > > an ftrace-based mechanism and kernel interface for doing live
On Fri 2014-11-21 11:39:24, Masami Hiramatsu wrote:
> (2014/11/21 7:29), Seth Jennings wrote:
> > This commit introduces code for the live patching core. It implements
> > an ftrace-based mechanism and kernel interface for doing live patching
> > of kernel and kernel module functions.
> >
> > It
On Fri 2014-11-21 11:39:24, Masami Hiramatsu wrote:
(2014/11/21 7:29), Seth Jennings wrote:
This commit introduces code for the live patching core. It implements
an ftrace-based mechanism and kernel interface for doing live patching
of kernel and kernel module functions.
It represents
On Tue, 25 Nov 2014 17:39:43 +0100
Petr Mladek pmla...@suse.cz wrote:
On Fri 2014-11-21 11:39:24, Masami Hiramatsu wrote:
(2014/11/21 7:29), Seth Jennings wrote:
This commit introduces code for the live patching core. It implements
an ftrace-based mechanism and kernel interface for
On Tue 2014-11-25 11:52:10, Steven Rostedt wrote:
On Tue, 25 Nov 2014 17:39:43 +0100
Petr Mladek pmla...@suse.cz wrote:
On Fri 2014-11-21 11:39:24, Masami Hiramatsu wrote:
(2014/11/21 7:29), Seth Jennings wrote:
This commit introduces code for the live patching core. It implements
On Tue, 25 Nov 2014 18:04:31 +0100
Petr Mladek pmla...@suse.cz wrote:
On Tue 2014-11-25 11:52:10, Steven Rostedt wrote:
On Tue, 25 Nov 2014 17:39:43 +0100
Petr Mladek pmla...@suse.cz wrote:
On Fri 2014-11-21 11:39:24, Masami Hiramatsu wrote:
(2014/11/21 7:29), Seth Jennings wrote:
On Tue, 25 Nov 2014, Steven Rostedt wrote:
It is not guaranteed from ftrace's stand point. What happens if we have
a kprobe handler that modifies it for someplace else? Changing the ip
address may not be a kpatch/kGraft privilege only.
This brings me back to the RFC patch I sent back then in
(2014/11/24 22:31), Vojtech Pavlik wrote:
> On Mon, Nov 24, 2014 at 02:26:08PM +0100, Thomas Gleixner wrote:
>> On Mon, 24 Nov 2014, Jiri Kosina wrote:
>>> On Mon, 24 Nov 2014, Thomas Gleixner wrote:
How is determined whether a change can be applied w/o a consistency
mechanism or not?
(2014/11/24 20:13), Thomas Gleixner wrote:
> On Thu, 20 Nov 2014, Seth Jennings wrote:
>> This commit introduces code for the live patching core. It implements
>> an ftrace-based mechanism and kernel interface for doing live patching
>> of kernel and kernel module functions.
>>
>> It represents
On Mon, Nov 24, 2014 at 02:26:08PM +0100, Thomas Gleixner wrote:
> On Mon, 24 Nov 2014, Jiri Kosina wrote:
> > On Mon, 24 Nov 2014, Thomas Gleixner wrote:
> > > How is determined whether a change can be applied w/o a consistency
> > > mechanism or not?
> >
> > By a human being producing the "live
On Mon, 24 Nov 2014, Thomas Gleixner wrote:
> > The person writing the patch would always need to understand what he is
> > doing to be able to pick correct consistency model to be used. I
> > personally think this is a good thing -- this is nothing where we should
> > be relying on any kinds
On Mon, 24 Nov 2014, Jiri Kosina wrote:
> On Mon, 24 Nov 2014, Thomas Gleixner wrote:
> > How is determined whether a change can be applied w/o a consistency
> > mechanism or not?
>
> By a human being producing the "live patch" code.
>
> If the semantics of the patch requires consistency
On Mon, Nov 24, 2014 at 12:13:20PM +0100, Thomas Gleixner wrote:
> On Thu, 20 Nov 2014, Seth Jennings wrote:
> > This commit introduces code for the live patching core. It implements
> > an ftrace-based mechanism and kernel interface for doing live patching
> > of kernel and kernel module
On Mon, Nov 24, 2014 at 12:13:20PM +0100, Thomas Gleixner wrote:
> > This commit introduces code for the live patching core. It implements
> > an ftrace-based mechanism and kernel interface for doing live patching
> > of kernel and kernel module functions.
> >
> > It represents the greatest
On Mon, 24 Nov 2014, Thomas Gleixner wrote:
> > This commit introduces code for the live patching core. It implements
> > an ftrace-based mechanism and kernel interface for doing live patching
> > of kernel and kernel module functions.
> >
> > It represents the greatest common functionality set
On Thu, 20 Nov 2014, Seth Jennings wrote:
> This commit introduces code for the live patching core. It implements
> an ftrace-based mechanism and kernel interface for doing live patching
> of kernel and kernel module functions.
>
> It represents the greatest common functionality set between
On Thu, 20 Nov 2014, Seth Jennings wrote:
This commit introduces code for the live patching core. It implements
an ftrace-based mechanism and kernel interface for doing live patching
of kernel and kernel module functions.
It represents the greatest common functionality set between kpatch
On Mon, 24 Nov 2014, Thomas Gleixner wrote:
This commit introduces code for the live patching core. It implements
an ftrace-based mechanism and kernel interface for doing live patching
of kernel and kernel module functions.
It represents the greatest common functionality set between
On Mon, Nov 24, 2014 at 12:13:20PM +0100, Thomas Gleixner wrote:
This commit introduces code for the live patching core. It implements
an ftrace-based mechanism and kernel interface for doing live patching
of kernel and kernel module functions.
It represents the greatest common
On Mon, Nov 24, 2014 at 12:13:20PM +0100, Thomas Gleixner wrote:
On Thu, 20 Nov 2014, Seth Jennings wrote:
This commit introduces code for the live patching core. It implements
an ftrace-based mechanism and kernel interface for doing live patching
of kernel and kernel module functions.
On Mon, 24 Nov 2014, Jiri Kosina wrote:
On Mon, 24 Nov 2014, Thomas Gleixner wrote:
How is determined whether a change can be applied w/o a consistency
mechanism or not?
By a human being producing the live patch code.
If the semantics of the patch requires consistency mechanism to be
(2014/11/24 20:13), Thomas Gleixner wrote:
On Thu, 20 Nov 2014, Seth Jennings wrote:
This commit introduces code for the live patching core. It implements
an ftrace-based mechanism and kernel interface for doing live patching
of kernel and kernel module functions.
It represents the greatest
On Mon, Nov 24, 2014 at 02:26:08PM +0100, Thomas Gleixner wrote:
On Mon, 24 Nov 2014, Jiri Kosina wrote:
On Mon, 24 Nov 2014, Thomas Gleixner wrote:
How is determined whether a change can be applied w/o a consistency
mechanism or not?
By a human being producing the live patch code.
On Mon, 24 Nov 2014, Thomas Gleixner wrote:
The person writing the patch would always need to understand what he is
doing to be able to pick correct consistency model to be used. I
personally think this is a good thing -- this is nothing where we should
be relying on any kinds of
(2014/11/24 22:31), Vojtech Pavlik wrote:
On Mon, Nov 24, 2014 at 02:26:08PM +0100, Thomas Gleixner wrote:
On Mon, 24 Nov 2014, Jiri Kosina wrote:
On Mon, 24 Nov 2014, Thomas Gleixner wrote:
How is determined whether a change can be applied w/o a consistency
mechanism or not?
By a human
On Fri, Nov 21, 2014 at 06:35:47PM +0100, Jiri Slaby wrote:
> On 11/21/2014, 05:40 PM, Seth Jennings wrote:
> >>> --- /dev/null
> >>> +++ b/arch/x86/include/asm/livepatch.h
> >>> @@ -0,0 +1,37 @@
> ...
> >>> +#ifndef _ASM_X86_LIVEPATCH_H
> >>> +#define _ASM_X86_LIVEPATCH_H
> >>> +
> >>> +#include
On Fri, Nov 21, 2014 at 8:40 AM, Seth Jennings wrote:
> On Fri, Nov 21, 2014 at 01:22:33AM +0100, Jiri Kosina wrote:
>> On Thu, 20 Nov 2014, Seth Jennings wrote:
>>
>> > This commit introduces code for the live patching core. It implements
>> > an ftrace-based mechanism and kernel interface for
On 11/21/2014, 05:40 PM, Seth Jennings wrote:
>>> --- /dev/null
>>> +++ b/arch/x86/include/asm/livepatch.h
>>> @@ -0,0 +1,37 @@
...
>>> +#ifndef _ASM_X86_LIVEPATCH_H
>>> +#define _ASM_X86_LIVEPATCH_H
>>> +
>>> +#include
>>> +
>>> +#ifdef CONFIG_LIVE_PATCHING
>>> +extern int
On Fri, Nov 21, 2014 at 01:22:33AM +0100, Jiri Kosina wrote:
> On Thu, 20 Nov 2014, Seth Jennings wrote:
>
> > This commit introduces code for the live patching core. It implements
> > an ftrace-based mechanism and kernel interface for doing live patching
> > of kernel and kernel module
On Fri, Nov 21, 2014 at 04:46:32PM +0100, Miroslav Benes wrote:
> On Fri, 21 Nov 2014, Josh Poimboeuf wrote:
>
> > On Fri, Nov 21, 2014 at 03:44:35PM +0100, Miroslav Benes wrote:
> > > On Fri, 21 Nov 2014, Jiri Kosina wrote:
> > >
> > > [...]
> > >
> > > > [ ... snip ... ]
> > > > > +static int
On Fri, 21 Nov 2014, Josh Poimboeuf wrote:
> On Fri, Nov 21, 2014 at 03:44:35PM +0100, Miroslav Benes wrote:
> > On Fri, 21 Nov 2014, Jiri Kosina wrote:
> >
> > [...]
> >
> > > [ ... snip ... ]
> > > > +static int klp_init_patch(struct klp_patch *patch)
> > > > +{
> > > > + int ret;
> > >
On Fri, Nov 21, 2014 at 04:27:57PM +0100, Jiri Kosina wrote:
> On Fri, 21 Nov 2014, Josh Poimboeuf wrote:
>
> > I think we can use "depends on HAVE_FENTRY" to accomplish this, since
> > CC_USING_FENTRY gets set by the top level kernel Makefile if
> > CONFIG_HAVE_FENTRY is set.
>
> The problem
On Fri, 21 Nov 2014, Josh Poimboeuf wrote:
> I think we can use "depends on HAVE_FENTRY" to accomplish this, since
> CC_USING_FENTRY gets set by the top level kernel Makefile if
> CONFIG_HAVE_FENTRY is set.
The problem is that HAVE_FENTRY is set automatically on x86_64, no matter
whether your
On Fri, Nov 21, 2014 at 01:22:33AM +0100, Jiri Kosina wrote:
> On Thu, 20 Nov 2014, Seth Jennings wrote:
> > --- /dev/null
> > +++ b/kernel/livepatch/Kconfig
> > @@ -0,0 +1,18 @@
> > +config ARCH_HAVE_LIVE_PATCHING
> > + boolean
> > + help
> > + Arch supports kernel live patching
> > +
> >
On Fri, Nov 21, 2014 at 03:44:35PM +0100, Miroslav Benes wrote:
> On Fri, 21 Nov 2014, Jiri Kosina wrote:
>
> [...]
>
> > [ ... snip ... ]
> > > +static int klp_init_patch(struct klp_patch *patch)
> > > +{
> > > + int ret;
> > > +
> > > + mutex_lock(_mutex);
> > > +
> > > + /* init */
> > > +
On Fri, 21 Nov 2014, Jiri Kosina wrote:
[...]
> [ ... snip ... ]
> > +static int klp_init_patch(struct klp_patch *patch)
> > +{
> > + int ret;
> > +
> > + mutex_lock(_mutex);
> > +
> > + /* init */
> > + patch->state = LPC_DISABLED;
> > +
> > + /* sysfs */
> > + ret =
On Fri, 21 Nov 2014, Jiri Kosina wrote:
[...]
[ ... snip ... ]
+static int klp_init_patch(struct klp_patch *patch)
+{
+ int ret;
+
+ mutex_lock(klp_mutex);
+
+ /* init */
+ patch-state = LPC_DISABLED;
+
+ /* sysfs */
+ ret = kobject_init_and_add(patch-kobj,
On Fri, Nov 21, 2014 at 03:44:35PM +0100, Miroslav Benes wrote:
On Fri, 21 Nov 2014, Jiri Kosina wrote:
[...]
[ ... snip ... ]
+static int klp_init_patch(struct klp_patch *patch)
+{
+ int ret;
+
+ mutex_lock(klp_mutex);
+
+ /* init */
+ patch-state = LPC_DISABLED;
On Fri, Nov 21, 2014 at 01:22:33AM +0100, Jiri Kosina wrote:
On Thu, 20 Nov 2014, Seth Jennings wrote:
--- /dev/null
+++ b/kernel/livepatch/Kconfig
@@ -0,0 +1,18 @@
+config ARCH_HAVE_LIVE_PATCHING
+ boolean
+ help
+ Arch supports kernel live patching
+
+config
On Fri, 21 Nov 2014, Josh Poimboeuf wrote:
I think we can use depends on HAVE_FENTRY to accomplish this, since
CC_USING_FENTRY gets set by the top level kernel Makefile if
CONFIG_HAVE_FENTRY is set.
The problem is that HAVE_FENTRY is set automatically on x86_64, no matter
whether your
On Fri, Nov 21, 2014 at 04:27:57PM +0100, Jiri Kosina wrote:
On Fri, 21 Nov 2014, Josh Poimboeuf wrote:
I think we can use depends on HAVE_FENTRY to accomplish this, since
CC_USING_FENTRY gets set by the top level kernel Makefile if
CONFIG_HAVE_FENTRY is set.
The problem is that
On Fri, 21 Nov 2014, Josh Poimboeuf wrote:
On Fri, Nov 21, 2014 at 03:44:35PM +0100, Miroslav Benes wrote:
On Fri, 21 Nov 2014, Jiri Kosina wrote:
[...]
[ ... snip ... ]
+static int klp_init_patch(struct klp_patch *patch)
+{
+ int ret;
+
+
On Fri, Nov 21, 2014 at 04:46:32PM +0100, Miroslav Benes wrote:
On Fri, 21 Nov 2014, Josh Poimboeuf wrote:
On Fri, Nov 21, 2014 at 03:44:35PM +0100, Miroslav Benes wrote:
On Fri, 21 Nov 2014, Jiri Kosina wrote:
[...]
[ ... snip ... ]
+static int klp_init_patch(struct
On Fri, Nov 21, 2014 at 01:22:33AM +0100, Jiri Kosina wrote:
On Thu, 20 Nov 2014, Seth Jennings wrote:
This commit introduces code for the live patching core. It implements
an ftrace-based mechanism and kernel interface for doing live patching
of kernel and kernel module functions.
On 11/21/2014, 05:40 PM, Seth Jennings wrote:
--- /dev/null
+++ b/arch/x86/include/asm/livepatch.h
@@ -0,0 +1,37 @@
...
+#ifndef _ASM_X86_LIVEPATCH_H
+#define _ASM_X86_LIVEPATCH_H
+
+#include linux/module.h
+
+#ifdef CONFIG_LIVE_PATCHING
+extern int klp_write_module_reloc(struct module
On Fri, Nov 21, 2014 at 8:40 AM, Seth Jennings sjenn...@redhat.com wrote:
On Fri, Nov 21, 2014 at 01:22:33AM +0100, Jiri Kosina wrote:
On Thu, 20 Nov 2014, Seth Jennings wrote:
This commit introduces code for the live patching core. It implements
an ftrace-based mechanism and kernel
On Fri, Nov 21, 2014 at 06:35:47PM +0100, Jiri Slaby wrote:
On 11/21/2014, 05:40 PM, Seth Jennings wrote:
--- /dev/null
+++ b/arch/x86/include/asm/livepatch.h
@@ -0,0 +1,37 @@
...
+#ifndef _ASM_X86_LIVEPATCH_H
+#define _ASM_X86_LIVEPATCH_H
+
+#include linux/module.h
+
+#ifdef
(2014/11/21 7:29), Seth Jennings wrote:
> This commit introduces code for the live patching core. It implements
> an ftrace-based mechanism and kernel interface for doing live patching
> of kernel and kernel module functions.
>
> It represents the greatest common functionality set between kpatch
On Thu, 20 Nov 2014, Seth Jennings wrote:
> This commit introduces code for the live patching core. It implements
> an ftrace-based mechanism and kernel interface for doing live patching
> of kernel and kernel module functions.
>
> It represents the greatest common functionality set between
This commit introduces code for the live patching core. It implements
an ftrace-based mechanism and kernel interface for doing live patching
of kernel and kernel module functions.
It represents the greatest common functionality set between kpatch and
kgraft and can accept patches built using
This commit introduces code for the live patching core. It implements
an ftrace-based mechanism and kernel interface for doing live patching
of kernel and kernel module functions.
It represents the greatest common functionality set between kpatch and
kgraft and can accept patches built using
On Thu, 20 Nov 2014, Seth Jennings wrote:
This commit introduces code for the live patching core. It implements
an ftrace-based mechanism and kernel interface for doing live patching
of kernel and kernel module functions.
It represents the greatest common functionality set between kpatch
(2014/11/21 7:29), Seth Jennings wrote:
This commit introduces code for the live patching core. It implements
an ftrace-based mechanism and kernel interface for doing live patching
of kernel and kernel module functions.
It represents the greatest common functionality set between kpatch and
58 matches
Mail list logo
