On Sat, Nov 24, 2012 at 1:07 PM, Eric W. Biederman
wrote:
> Ian Kent writes:
>
>> On Sat, 2012-11-24 at 10:23 +0800, Ian Kent wrote:
>>> On Fri, 2012-11-23 at 15:30 +0100, Miklos Szeredi wrote:
>>> AFAICS autofs mounts mounted with MS_PRIVATE in the initial namespace do
>>> propagate to the clon
Otherwise we are getting a nil dereference
| [0.00] BUG: unable to handle kernel NULL pointer dereference at
(null)
| [0.00] IP: [] strcmp+0x10/0x30
Signed-off-by: Cyrill Gorcunov
---
mm/percpu.c |3 +++
1 file changed, 3 insertions(+)
Index: linux-2.6.git/mm/p
On Sat, Nov 24, 2012 at 11:50 AM, H. Peter Anvin wrote:
> On 11/24/2012 09:32 AM, H. Peter Anvin wrote:
>>
>> On 11/24/2012 04:37 AM, Eric W. Biederman wrote:
>>>
>>>
>>> Certainly /sbin/kexec isn't bothering to calculate the end of the setup
>>> header and just being far more conservative and usi
On 11/24/2012 01:30 PM, Yinghai Lu wrote:
So, given the mess we now have on our hands... any suggestions how to best
solve it? There is the option of simply declaring old kexec binaries
broken; they will then not work reliably with newer kernels, if they even
work reliably now -- it is hard to
On Thursday, November 08, 2012 01:23:44 PM Toshi Kani wrote:
> Added a new .sys_notify interface, which allows ACPI drivers to
> register their system-level (ex. hotplug) notify handlers through
> their acpi_driver table. This removes redundant ACPI namespace
> walks from ACPI drivers for faster b
On Saturday, November 24, 2012 11:01:56 PM Rafael J. Wysocki wrote:
> On Thursday, November 08, 2012 01:23:44 PM Toshi Kani wrote:
> > Added a new .sys_notify interface, which allows ACPI drivers to
> > register their system-level (ex. hotplug) notify handlers through
> > their acpi_driver table.
On Sat, Nov 24, 2012 at 1:38 PM, H. Peter Anvin wrote:
> On 11/24/2012 01:30 PM, Yinghai Lu wrote:
>>>
>>>
>>> So, given the mess we now have on our hands... any suggestions how to
>>> best
>>> solve it? There is the option of simply declaring old kexec binaries
>>> broken; they will then not wor
On 11/24/2012 02:18 PM, Yinghai Lu wrote:
Careful... consider the people who use a kexec-based solution as
bootloaders.
yes, those may not update kexec in the flash...
then, may need to use another bit in xloadflags to tell new kernel if
need to check ext_...
Field name: xloadflags
Type:
On Saturday, November 24, 2012 11:01:56 PM Rafael J. Wysocki wrote:
> On Thursday, November 08, 2012 01:23:44 PM Toshi Kani wrote:
> > Added a new .sys_notify interface, which allows ACPI drivers to
> > register their system-level (ex. hotplug) notify handlers through
> > their acpi_driver table.
Miklos Szeredi writes:
> On Sat, Nov 24, 2012 at 1:07 PM, Eric W. Biederman
> wrote:
>> Ian Kent writes:
>>
>>> On Sat, 2012-11-24 at 10:23 +0800, Ian Kent wrote:
On Fri, 2012-11-23 at 15:30 +0100, Miklos Szeredi wrote:
>
AFAICS autofs mounts mounted with MS_PRIVATE in the initial nam
Rafael,
On Sat, Nov 24, 2012 at 2:03 AM, Rafael J. Wysocki wrote:
> On Monday, November 12, 2012 10:00:07 PM Arnd Bergmann wrote:
>> On Wednesday 07 November 2012, Rob Herring wrote:
>> > From: Rob Herring
>> >
>> > Add support for core powergating on Calxeda platforms. Initially, this
>> > supp
On Sun, Nov 25, 2012 at 5:09 AM, Mikulas Patocka wrote:
> So it's better to slow down mount.
I am quite proud of the linux boot time pitting against other OS. Even
with 10 partitions. Linux can boot up in just a few seconds, but now
you're saying that we need to do this semaphore check at boot up
On Sat, Nov 24, 2012 at 2:32 PM, H. Peter Anvin wrote:
> On 11/24/2012 02:18 PM, Yinghai Lu wrote:
> Well, that solves the problem for *this specific instance* but I fear
> therein lies madness in the general case.
>
use
Bit 0 (read): CAN_BE_LOADED_ABOVE_4G
- If 1, kernel/boot_param
On Saturday, November 24, 2012 03:21:49 PM Olof Johansson wrote:
> Rafael,
>
> On Sat, Nov 24, 2012 at 2:03 AM, Rafael J. Wysocki wrote:
> > On Monday, November 12, 2012 10:00:07 PM Arnd Bergmann wrote:
> >> On Wednesday 07 November 2012, Rob Herring wrote:
> >> > From: Rob Herring
> >> >
> >> >
"H. Peter Anvin" writes:
> On 11/24/2012 09:32 AM, H. Peter Anvin wrote:
>> On 11/24/2012 04:37 AM, Eric W. Biederman wrote:
>>>
>>> Certainly /sbin/kexec isn't bothering to calculate the end of the setup
>>> header and just being far more conservative and using all of the 16bit
>>> real mode cod
On Sat, Nov 24, 2012 at 3:50 PM, Eric W. Biederman
wrote:
>
> I believe all added variables between the last version of the boot
> protocol /sbin/kexec knows about and the current time were added in the
> initialized data section. Certainly we can check and that will tell us
> how likely changes
On 11/24/2012 03:50 PM, Eric W. Biederman wrote:
It was conservative at the time the code was introduced and it most
definitely is not wrong. The code predates the verbage in boot.txt.
Apparently no one bothered to see what /sbin/kexec was actually doing
when they documented the 32bit boot load
On 11/24/2012 04:04 PM, Yinghai Lu wrote:
On Sat, Nov 24, 2012 at 3:50 PM, Eric W. Biederman
wrote:
I believe all added variables between the last version of the boot
protocol /sbin/kexec knows about and the current time were added in the
initialized data section. Certainly we can check and t
>Could you take few snapshots over time?
Here it is, now from different server, snapshot was taken every second for 10
minutes (hope it's enough):
www.watchdog.sk/lkml/memcg-bug-2.tar.gz
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord
On Sat, Nov 24, 2012 at 4:04 PM, H. Peter Anvin wrote:
>
> It sounds like we are leaning toward some form of the sentinel hack, which
> means we need an enumerated list of things that should *not* be zeroed if
> the sentinel is present.
>
> The option of declaring the list frozen makes me a bit ne
On Sat, Nov 24, 2012 at 12:35 PM, Yinghai Lu wrote:
> ext_ramdisk_image/size will record high 32bits for ramdisk info.
>
> xloadflags bit0 will be set if relocatable with 64bit.
>
> Let get_ramdisk_image/size to use ext_ramdisk_image/size to get
> right positon for ramdisk.
>
> bootloader will fil
Found using the following semantic patch:
@@
@@
spin_lock_irqsave(...);
... when != spin_unlock_irqrestore(...);
* GFP_KERNEL
Signed-off-by: Cyril Roelandt
---
drivers/usb/gadget/uvc_video.c |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/usb/gadget/uvc_video.c
On Thu, Nov 22, 2012 at 9:49 PM, Michel Lespinasse wrote:
> On Thu, Nov 22, 2012 at 9:14 AM, Sasha Levin wrote:
>> The following patch fixed the problem for me:
>>
>> diff --git a/include/linux/rbtree_augmented.h
>> b/include/linux/rbtree_augmented.h
>> index 214caa3..5cfdca6 100644
>> --- a/inc
The rbtree interval API is designed for handling non-overlapping intervals;
modify rb_int_insert() to guarantee this property is maintained by
returning -EEXIST when attempting to insert a new interval that overlaps
an existing interval.
Also fix an issue where the computation of 'result' could tr
As the rbtree intervals are not overlapping, rb_int_search_single can
trivially be implemented without making use of the max_high field.
Signed-off-by: Michel Lespinasse
---
tools/kvm/util/rbtree-interval.c | 18 +-
1 files changed, 5 insertions(+), 13 deletions(-)
diff --git
Since nothing depends on the max_high field values anymore, we can just
remove the field and the code that was used to maintain it.
Signed-off-by: Michel Lespinasse
---
tools/kvm/include/kvm/rbtree-interval.h | 13 ---
tools/kvm/util/rbtree-interval.c| 58 +--
On Sat, Nov 24, 2012 at 11:41:23AM +0200, Pekka Enberg wrote:
> On Sat, Nov 24, 2012 at 10:29 AM, wrote:
> > For old glibc there's no the syscall number this tests will cause
> > make run_tests fail.
> > Add a macro to define the number. This should be ok because it will be
> > built in latest ke
This patch applies spinlock to protect access to rx / tx structs in
certain call sites, which fixes the following crash in gdm_suspend.
It also fixes usb_set_intfdata() in gdm_usb_probe to avoid setting an
already freed phy_dev.
<5>[ 4996.815018] [<7f0074b0>] (gdm_suspend+0x1c/0x2b4 [gdmwm]) from
On Sat, Nov 24, 2012 at 4:11 PM, Yinghai Lu wrote:
> On Sat, Nov 24, 2012 at 4:04 PM, H. Peter Anvin wrote:
>>
>> It sounds like we are leaning toward some form of the sentinel hack, which
>> means we need an enumerated list of things that should *not* be zeroed if
>> the sentinel is present.
>>
But it doesn't solve the bigger problem, and it is just begging to be gotten
wrong.
Yinghai Lu wrote:
>On Sat, Nov 24, 2012 at 4:11 PM, Yinghai Lu wrote:
>> On Sat, Nov 24, 2012 at 4:04 PM, H. Peter Anvin
>wrote:
>>>
>>> It sounds like we are leaning toward some form of the sentinel hack,
>wh
as per 4) move towards where "most" memory. If we have a large shared
memory than private memnory. Why not we just move the process towrds
the memory.. instead of the memory moving towards the node. This will
i guess be less cumbersome, then moving all the shared memory
On Fri, Nov 16, 2012 at 9:5
On Sat, Nov 24, 2012 at 9:52 PM, H. Peter Anvin wrote:
> But it doesn't solve the bigger problem, and it is just begging to be gotten
> wrong.
>>
>>later all new kernel need to check USE_EXT_BOOT_PARAMS bit for all new
>>added field in boot_params.
Do you mean
later someone would forget checking
On 11/24/12, Mel Gorman wrote:
> On Sat, Nov 24, 2012 at 12:17:03PM +0800, Hillf Danton wrote:
>> A thp contributes 512 times more than a regular page to numa fault stats,
>> so deserves its own vm event counter. THP migration is also accounted.
>>
>
> I agree and mentioned it needed fixing. I did
Hi Xiaotian,
On Wed, Oct 31, 2012 at 04:05:59PM +0800, Xiaotian Feng wrote:
> If tasklet_disable() is called before related tasklet handled,
> tasklet_kill will never be finished. tasklet_kill is enough.
>
Could you please elaborate on this? Needing to disable tasket before
killing it is quite o
101 - 134 of 134 matches
Mail list logo
