[PATCH 000 of 2] md: Introduction

Two patches to fix two possibly Oopses in md/raid
Both are suitable for 2.6.17.

Both involve indexing off the end of the array, and only cause a
problem if the ends up hitting a non-mapped page.

The first only affects raid0 is fairly rare put possible circumstances.

The second can affect all users of bio_split: linear, raid0, raid10

Thanks to Don Dupuis for hitting these bugs!

 [PATCH 001 of 2] md: Fix possible oops when starting a raid0 array
 [PATCH 002 of 2] md: Make sure bi_max_vecs is set properly in bio_split
-
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 002 of 2] md: Make sure bi_max_vecs is set properly in bio_split
    • From: NeilBrown <[email protected]>
  • [PATCH 001 of 2] md: Fix possible oops when starting a raid0 array
    • From: NeilBrown <[email protected]>

• Prev by Date: Re: __vmalloc with GFP_ATOMIC causes 'sleeping from invalid context'
• Next by Date: [PATCH 001 of 2] md: Fix possible oops when starting a raid0 array
• Previous by thread: Re: signal handling (clarification needed)
• Next by thread: [PATCH 001 of 2] md: Fix possible oops when starting a raid0 array
• 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]