search for: ebiederm

...gt; If there is no entry, it will simply return with -EINVAL. > > [1] > https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-firmware-memmap You know what this justification is rubbish, and I have previously explained why it is rubbish. Nacked-by: "Eric W. Biederman" <ebiederm at xmission.com> This needs to be based on weather the added memory is ultimately normal ram or is something special. At least when we are talking memory resources. Keeping it out of the firmware map that is fine. If the hotplugged memory is the result of plugging a stick of ram into the ker...

...gt; If there is no entry, it will simply return with -EINVAL. > > [1] > https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-firmware-memmap You know what this justification is rubbish, and I have previously explained why it is rubbish. Nacked-by: "Eric W. Biederman" <ebiederm at xmission.com> This needs to be based on weather the added memory is ultimately normal ram or is something special. At least when we are talking memory resources. Keeping it out of the firmware map that is fine. If the hotplugged memory is the result of plugging a stick of ram into the ker...

...linux-ext4@vger.kernel.org S: Maintained @@ -1901,7 +1901,7 @@ JOURNALLING LAYER FOR BLOCK DEVICES (JBD) P: Stephen Tweedie, Andrew Morton -M: sct@redhat.com, akpm@osdl.org +M: sct@redhat.com, akpm@linux-foundation.org L: linux-ext4@vger.kernel.org S: Maintained @@ -1972,7 +1972,7 @@ M: ebiederm@xmission.com W: http://www.xmission.com/~ebiederm/files/kexec/ L: linux-kernel@vger.kernel.org -L: fastboot@osdl.org +L: fastboot@lists.osdl.org S: Maintained KPROBES @@ -2310,7 +2310,7 @@ NETEM NETWORK EMULATOR P: Stephen Hemminger M: shemminger@linux-foundation.org -L: netem@osdl.org +L:...

...illed we try to clean up the SIGKLL by doing a sigdelset and recalc_sigpending, but we still leave it in shared_pending. If the signal is being short circuit delivered there is no need to put in shared_pending so this adds a check in complete_signal. This patch was modified from Eric Biederman <ebiederm at xmission.com> original patch. Signed-off-by: Mike Christie <michael.christie at oracle.com> --- kernel/signal.c | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/kernel/signal.c b/kernel/signal.c index 8f6330f0e9ca..3dc99b9aec7f 100644 --- a/kernel/signal.c +++ b/kernel/sign...

...goto drop; >> > >> > /* >> > >> > So this is just an optimization. >> > >> > The test itself was added in >> > >> > ommit e730c15519d09ea528b4d2f1103681fa5937c0e6 >> > Author: Eric W. Biederman <ebiederm at xmission.com> >> > Date: Mon Sep 17 11:53:39 2007 -0700 >> > >> > [NET]: Make packet reception network namespace safe >> > >> > This patch modifies every packet receive function >> > registered with dev_add_pack() to...

...; > Cc: Kees Cook <keescook at chromium.org> > Cc: Ard Biesheuvel <ardb at kernel.org> > Cc: Pankaj Gupta <pankaj.gupta.linux at gmail.com> > Cc: Baoquan He <bhe at redhat.com> > Cc: Wei Yang <richardw.yang at linux.intel.com> > Cc: Eric Biederman <ebiederm at xmission.com> > Cc: Thomas Gleixner <tglx at linutronix.de> > Cc: Greg Kroah-Hartman <gregkh at linuxfoundation.org> > Cc: kexec at lists.infradead.org > Signed-off-by: David Hildenbrand <david at redhat.com> > --- > include/linux/ioport.h | 4 +++- > k...

Some concern was expressed over the lguest review status, so I shall send the patches out again for people to review, to test, to make observations about the author's personal appearance, etc. I'll plan on sending these patches off to Linus in a week's time, assuming all goes well. Thanks. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body

Some concern was expressed over the lguest review status, so I shall send the patches out again for people to review, to test, to make observations about the author's personal appearance, etc. I'll plan on sending these patches off to Linus in a week's time, assuming all goes well. Thanks. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body

This is the follow up of [1]: [PATCH v1 0/3] mm/memory_hotplug: Make virtio-mem play nicely with kexec-tools I realized that this is not only helpful for virtio-mem, but also for dax/kmem - it's a fix for that use case (see patch #3) of persistent memory. Also, while testing, I discovered that kexec-tools will *not* add dax/kmem memory (anything not directly under the root when parsing

...core. Reported-by: Fam Zheng <famz at redhat.com> Cc: Bjorn Helgaas <bhelgaas at google.com> Cc: Yinghai Lu <yhlu.kernel.send at gmail.com> Cc: Ulrich Obergfell <uobergfe at redhat.com> Cc: Rusty Russell <rusty at rustcorp.com.au> Cc: "Eric W. Biederman" <ebiederm at xmission.com> Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- changes from v6: limit changes to virtio only changes from v5: rebased on top of pci/msi fixed commit log, including comments by Bjorn and adding explanation to address comments/questions...

...core. Reported-by: Fam Zheng <famz at redhat.com> Cc: Bjorn Helgaas <bhelgaas at google.com> Cc: Yinghai Lu <yhlu.kernel.send at gmail.com> Cc: Ulrich Obergfell <uobergfe at redhat.com> Cc: Rusty Russell <rusty at rustcorp.com.au> Cc: "Eric W. Biederman" <ebiederm at xmission.com> Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- changes from v6: limit changes to virtio only changes from v5: rebased on top of pci/msi fixed commit log, including comments by Bjorn and adding explanation to address comments/questions...

...sn't set this, then we simply do the normal boot sequence. Signed-off-by: Jeremy Fitzhardinge <jeremy@xensource.com> Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> Acked-by: H. Peter Anvin <hpa@zytor.com> Cc: "Eric W. Biederman" <ebiederm@xmission.com> Cc: Vivek Goyal <vgoyal@in.ibm.com> Cc: James Bottomley <James.Bottomley@HansenPartnership.com> commit a706681568ed19f147ab78674388c5a0e6ab8c44 Author: Jeremy Fitzhardinge <jeremy@xensource.com> Date: Mon Oct 22 10:56:18 2007 +1000 add WEAK() for c...

...sn't set this, then we simply do the normal boot sequence. Signed-off-by: Jeremy Fitzhardinge <jeremy@xensource.com> Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> Acked-by: H. Peter Anvin <hpa@zytor.com> Cc: "Eric W. Biederman" <ebiederm@xmission.com> Cc: Vivek Goyal <vgoyal@in.ibm.com> Cc: James Bottomley <James.Bottomley@HansenPartnership.com> commit a706681568ed19f147ab78674388c5a0e6ab8c44 Author: Jeremy Fitzhardinge <jeremy@xensource.com> Date: Mon Oct 22 10:56:18 2007 +1000 add WEAK() for c...

This is based on an earlier patch from Eric Biederman adding forwarding between macvlans. I extended his approach to allow the administrator to choose the mode for each macvlan, and to implement a functional VEPA between macvlan. Still missing from this is support for communication between the lower device that the macvlans are based on. This would be extremely useful but as others have found out

This is based on an earlier patch from Eric Biederman adding forwarding between macvlans. I extended his approach to allow the administrator to choose the mode for each macvlan, and to implement a functional VEPA between macvlan. Still missing from this is support for communication between the lower device that the macvlans are based on. This would be extremely useful but as others have found out

This is based on an earlier patch from Eric Biederman adding forwarding between macvlans. I extended his approach to allow the administrator to choose the mode for each macvlan, and to implement a functional VEPA between macvlan. Still missing from this is support for communication between the lower device that the macvlans are based on. This would be extremely useful but as others have found out

...why this is the right thing to do *for special memory*, *not > ordinary DIMMs*. > > And to be quite honest, I think your response is a little harsh. I don't > recall you replying to my virtio-mem-related comments. > >> >> Nacked-by: "Eric W. Biederman" <ebiederm at xmission.com> >> >> This needs to be based on weather the added memory is ultimately normal >> ram or is something special. > > Yes, that's what the caller are expected to decide, see patch #3. > > kexec should try to be as closely as possible to a real rebo...

...why this is the right thing to do *for special memory*, *not > ordinary DIMMs*. > > And to be quite honest, I think your response is a little harsh. I don't > recall you replying to my virtio-mem-related comments. > >> >> Nacked-by: "Eric W. Biederman" <ebiederm at xmission.com> >> >> This needs to be based on weather the added memory is ultimately normal >> ram or is something special. > > Yes, that's what the caller are expected to decide, see patch #3. > > kexec should try to be as closely as possible to a real rebo...

This series is based on [1]: [PATCH v2 00/10] virtio-mem: paravirtualized memory That will hopefull get picked up soon, rebased to -next. The following patches were reverted from -next [2]: [PATCH 0/3] kexec/memory_hotplug: Prevent removal and accidental use As discussed in that thread, they should be reverted from -next already. In theory, if people agree, we could take the first two patches

fre, 27 03 2009 kl. 10:22 +1030, skrev Rusty Russell: > From: Matias Zabaljauregui <zabaljauregui at gmail.com> > > Impact: cleanup > > This patch allow us to use KVM hypercalls Something has broken in relation to this change. I'm not sure it is this change itself or one following, but I get the following error when using lguest: lguest: unhandled trap 6 at 0x418726