From: Guo Chao <yan@linux.vnet.ibm.com>
To: axboe@kernel.dk
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH 0/7] Loop device bug fix
Date: Fri, 25 Jan 2013 18:56:15 +0800 [thread overview]
Message-ID: <1359111382-12654-1-git-send-email-yan@linux.vnet.ibm.com> (raw)
This patchset fix several loop device bugs.
Patch #1 fix non-atomic updating block device size. It also prepares for
a later dead lock patch.
Patch #2 is a trivial clean up about block device.
The rest of the patchset are loop device fix:
#3 - fix a dead loop
#4 - fix a race-like problem
#5 - a little clean up based on #3 and #4
#6 - fix a user triggable oops
#7 - avoid loop device size being messed up by parameters from users
Guo Chao (7):
block: use i_size_write() in bd_set_size()
block: remove redundant check to bd_openers
loopdev: fix a dead lock
loopdev: update block device size in loop_set_status()
loopdev: move common code into loop_figure_size()
loopdev: remove an user triggable oops
loopdev: ignore negative offset when calculate loop device size
drivers/block/loop.c | 61 ++++++++++++++++++++++++--------------------------
fs/block_dev.c | 6 +++--
2 files changed, 33 insertions(+), 34 deletions(-)
--
1.7.9.5
next reply other threads:[~2013-01-25 10:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-25 10:56 Guo Chao [this message]
2013-01-25 10:56 ` [PATCH 1/7] block: use i_size_write() in bd_set_size() Guo Chao
2013-01-25 10:56 ` [PATCH 2/7] block: remove redundant check to bd_openers Guo Chao
2013-01-25 10:56 ` [PATCH 3/7] loopdev: fix a dead lock Guo Chao
2013-01-25 10:56 ` [PATCH 4/7] loopdev: update block device size in loop_set_status() Guo Chao
2013-01-25 10:56 ` [PATCH 5/7] loopdev: move common code into loop_figure_size() Guo Chao
2013-01-25 10:56 ` [PATCH 6/7] loopdev: remove an user triggable oops Guo Chao
2013-01-25 10:56 ` [PATCH 7/7] loopdev: ignore negative offset when calculate loop device size Guo Chao
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=1359111382-12654-1-git-send-email-yan@linux.vnet.ibm.com \
--to=yan@linux.vnet.ibm.com \
--cc=axboe@kernel.dk \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome