Re: [BUGFIX] NULL pointer dereference in __vm_enough_memory()

On Sat, Aug 11, 2007 at 11:31:09PM +0530, Balbir Singh wrote:
> Andrew Morton wrote:
> > On Sat, 11 Aug 2007 20:00:12 +0530 "Balbir Singh" <[email protected]> wrote:
> >>>
> >> Shouldn't we just not stop vm accounting for kernel threads?
> >>
> > 
> > Could be.  It'd help heaps if we knew which patch in -mm caused
> > this, but from a quick peek it seems to me that mainline should be
> > vulnerable as well.
> 
> Thats a valid point. It would be interesting to see what the overcommit
> setting was, when the panic occurred.

FYI, I do have nondefault overcommit settings:

vm.overcommit_memory = 2
vm.lowmem_reserve_ratio = 1 1

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • [BUGFIX] NULL pointer dereference in __vm_enough_memory()
    • From: Fengguang Wu <[email protected]>
  • Re: [BUGFIX] NULL pointer dereference in __vm_enough_memory()
    • From: "Balbir Singh" <[email protected]>
  • Re: [BUGFIX] NULL pointer dereference in __vm_enough_memory()
    • From: Andrew Morton <[email protected]>
  • Re: [BUGFIX] NULL pointer dereference in __vm_enough_memory()
    • From: Balbir Singh <[email protected]>

• Prev by Date: Re: [BUGFIX] NULL pointer dereference in __vm_enough_memory()
• Next by Date: Re: [PATCH] make atomic_t volatile on all architectures
• Previous by thread: Re: [BUGFIX] NULL pointer dereference in __vm_enough_memory()
• Next by thread: Re: [BUGFIX] NULL pointer dereference in __vm_enough_memory()
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]