From: Neil Brown <neilb@suse.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-raid@vger.kernel.org, stable@kernel.org
Subject: [PULL-REQUEST] md: avoid bogus read error on large-PAGE_SIZE machines
Date: Fri, 19 Dec 2008 16:44:19 +1100 [thread overview]
Message-ID: <18763.13491.611860.250273@notabene.brown> (raw)
Hoping this isn't too late for 2.6.28.
This fixes a bug that makes it impossible to start md arrays with
write-intent-bitmaps on machines with 64K PAGE_SIZE.
We read whole pages and as easily fall off the end of the device.
It is a bug that has been around for a long time and is suitable for
any currently maintained -stable. As such it has a
Cc: stable@kernel.org
line.
Thanks,
NeilBrown
The following changes since commit 55dac3a5553b13891f0ae4bbd11920619b5436d4:
Linus Torvalds (1):
Merge branch 'i2c-fixes' of git://aeryn.fluff.org.uk/bjdooks/linux
are available in the git repository at:
git://neil.brown.name/md/ for-linus
NeilBrown (1):
md: Don't read past end of bitmap when reading bitmap.
drivers/md/bitmap.c | 22 +++++++++++++++++-----
1 files changed, 17 insertions(+), 5 deletions(-)
reply other threads:[~2008-12-19 5:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=18763.13491.611860.250273@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=stable@kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox