Re: [patch 0/2] Protect crashkernel against BSS overlap

Vivek Goyal <[email protected]> writes:

> Wouldn't it be better if we reserve the code, data and bss memory also
> using bootmem allocator and when somebody tries to reserve craskernel memory
> and if there is an overlap, boot memory allocator should scream?

Some x86 bootmem code right now relies on it not screaming (or at least not
erroring out). That would need to be fixed first. Or you make it a flag.
Would probably make sense, except that we already have too many bootmem
allocation variants :/

-Andi
-
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:
  • Re: [patch 0/2] Protect crashkernel against BSS overlap
    • From: Bernhard Walle <[email protected]>

• References:
  • [patch 0/2] Protect crashkernel against BSS overlap
    • From: Bernhard Walle <[email protected]>
  • Re: [patch 0/2] Protect crashkernel against BSS overlap
    • From: Vivek Goyal <[email protected]>

• Prev by Date: Re: [BUG] 2.6.23-git8 kernel oops at __rb_rotate_left+0x7/0x70
• Next by Date: Re: [BUG] 2.6.23-git8 kernel oops at __rb_rotate_left+0x7/0x70
• Previous by thread: Re: [patch 0/2] Protect crashkernel against BSS overlap
• Next by thread: Re: [patch 0/2] Protect crashkernel against BSS overlap
• 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]