Re: kmalloc zero size changes break i386

On Fri, 20 Jul 2007, Pekka J Enberg wrote:
> There's some heavy-duty function inlining going on in__kmalloc so could 
> you please work out the exact location of the oops as described in 
> Documentation/BUG-HUNTING (look for the "use GDB to translate" part).

And, of course, please check if a5c96d8a1c67f31ef48935a78da2d2076513842b 
fixes it.

				Pekka
-
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/

---

• Follow-Ups:
  • [PATCH] Fix ZERO_OR_NULL_PTR(ZERO_SIZE_PTR)
    • From: Roland Dreier <[email protected]>

• References:
  • kmalloc zero size changes break i386
    • From: Andi Kleen <[email protected]>
  • Re: kmalloc zero size changes break i386
    • From: "Pekka Enberg" <[email protected]>
  • Re: kmalloc zero size changes break i386
    • From: Roland Dreier <[email protected]>
  • Re: kmalloc zero size changes break i386
    • From: Pekka J Enberg <[email protected]>

• Prev by Date: Re: [PATCH] kill DECLARE_MUTEX_LOCKED
• Next by Date: Re: [PATCH] mm: Fix memory hotplug oops from ZONE_MOVABLE changes.
• Previous by thread: Re: kmalloc zero size changes break i386
• Next by thread: [PATCH] Fix ZERO_OR_NULL_PTR(ZERO_SIZE_PTR)
• 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]