mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@gmail.com>
To: Jens Axboe <axboe@kernel.dk>, Nick Piggin <npiggin@kernel.dk>
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH 0/5] brd: partition handling fixes
Date: Thu, 26 May 2011 21:55:52 +0900	[thread overview]
Message-ID: <1306414557-2441-1-git-send-email-namhyung@gmail.com> (raw)

Hello.

This is a patch set for fixing bugs on partition handling code which
was found when I read loop block device code as well as some cleanups.

The patch 2/5 and 3/5 are real fixes and should go to the stable tree
as Jens suggested on loop patches. Since partition managing code was
introduced by commit d7853d1f8932 ("brd: modify ramdisk device to be
able to manage partitions") all stable releases would need these fixes.

  $ git name-rev --tags d7853d1f8932
  d7853d1f8932 tags/v2.6.26-rc1~122

As always, any comments are welcomed.
Thanks.


Namhyung Kim (5):
  brd: get rid of unused members from struct brd_device
  brd: limit 'max_part' module param to DISK_MAX_PARTS
  brd: handle on-demand devices correctly
  brd: fix comment on initial device creation
  brd: export module parameters

 drivers/block/brd.c |   42 ++++++++++++++++++++++++++----------------
 1 files changed, 26 insertions(+), 16 deletions(-)

--
1.7.5.2


             reply	other threads:[~2011-05-26 12:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-26 12:55 Namhyung Kim [this message]
2011-05-26 12:55 ` [PATCH 1/5] brd: get rid of unused members from struct brd_device Namhyung Kim
2011-05-26 12:55 ` [PATCH 2/5] brd: limit 'max_part' module param to DISK_MAX_PARTS Namhyung Kim
2011-05-26 12:55 ` [PATCH 3/5] brd: handle on-demand devices correctly Namhyung Kim
2011-05-26 12:55 ` [PATCH 4/5] brd: fix comment on initial device creation Namhyung Kim
2011-05-26 12:55 ` [PATCH 5/5] brd: export module parameters Namhyung Kim
2011-05-26 19:09 ` [PATCH 0/5] brd: partition handling fixes Jens Axboe

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=1306414557-2441-1-git-send-email-namhyung@gmail.com \
    --to=namhyung@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=npiggin@kernel.dk \
    /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

all inboxes | Powered by JetHome®