linux-kernel - Re: [PULL REQUEST] 2 (or 3) bug fixes for drives/md in 2.6.29

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <18827.57641.200482.849596@notabene.brown>
Date:	Fri, 6 Feb 2009 18:05:13 +1100
From:	Neil Brown <neilb@...e.de>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	linux-kernel@...r.kernel.org, linux-raid@...r.kernel.org,
	Andre Noll <maan@...temlinux.org>
Subject: Re: [PULL REQUEST] 2 (or 3) bug fixes for drives/md in 2.6.29

On Friday February 6, neilb@...e.de wrote:
> 
> Two small patches for md.
> The first is marked for -stable.

Make that three patches - I just found another bug (or maybe a missing
but very important feature).  It is for -stable too.

Thanks,
NeilBrown

The following changes since commit eda58a85ec3fc05855a26654d97a2b53f0e715b9:
  Linus Torvalds (1):
        Merge branch 'for-linus' of git://git.kernel.org/.../cooloney/blackfin-2.6

are available in the git repository at:

  git://neil.brown.name/md/ for-linus

Andre Noll (1):
      md: Fix a bug in linear.c causing which_dev() to return the wrong device.

NeilBrown (2):
      md: Allow read error in a single drive raid1 to be passed up.
      md: Ensure an md array never has too many devices.

 drivers/md/linear.c |    6 +++---
 drivers/md/md.c     |   24 ++++++++++++++----------
 drivers/md/raid1.c  |    3 ++-
 3 files changed, 19 insertions(+), 14 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/