mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dmitry Monakhov <dmonakhov@openvz.org>
To: Boaz Harrosh <boaz@plexistor.com>, Jens Axboe <axboe@fb.com>,
	Matthew Wilcox <willy@linux.intel.com>
Cc: Ross Zwisler <ross.zwisler@linux.intel.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCHSET 0/5 v2] brd: partition fixes
Date: Wed, 27 Aug 2014 19:45:48 +0400	[thread overview]
Message-ID: <87wq9u7x77.fsf@openvz.org> (raw)
In-Reply-To: <53FDF7AD.5000709@plexistor.com>

On Wed, 27 Aug 2014 18:22:21 +0300, Boaz Harrosh <boaz@plexistor.com> wrote:
> Jens Hi
> 
> What do you intend to do with these fixes? These are real bugs on devices
> shipped for a while now. I think they need to go into current 3.17-rcX Kernel.
> 
> If not then lets please put them in for-next
> [This set is for linux-block.git/for-next, tell me if you need one ontop
>  of for-linus]
> 
It looks like I've missed your context. Please elaborate your use-case
> [v2]
> Based on Jens's linux-next [30e996a] incorporating the brd patch by Dmitry Monakhov.
> Dmitry has introduced a new part_show parameter, this parameter is now
> removed
  In which commit or kernel-tree this parameter was removed?
> and we always "part_show=1".
> Scripts that did part_show=1 will work just the same but will display a
> message in logs. This is harmless. (And scripts can be modified to
> remove this parameter)
  Which script are you talking about? Why you want use it?

> 
> [v1]
> Current situation is that any attempt to use partitions with brd device would
> create the partition but then any use will trash the data.
> 
> See: http://www.spinics.net/lists/linux-scsi/msg76737.html
> 
> So these patches fixes up all the problems we saw with the code, but not sacrificing
> any of the old fixtures. See [patch 4/5] for more explanations.
> 
> list of patches:
> [PATCH 1/5] axonram: Fix bug in direct_access
> [PATCH 2/5] Change direct_access calling convention
> 
>     These are Matthew's patches from the DAX series which fixes the interface to
>     direct_access taking into account the partition offset. It must be applied
>     here for partitions to work with direct_access() API.
> 
> [PATCH 3/5] brd: Add getgeo to block ops
> 
>     This one is needed by fdisk, otherwise it just asks extra questions
> 
> [PATCH 4/5] brd: Fix all partitions BUGs
> [PATCH 5/5] brd: Request from fdisk 4k alignment
> 
> Thanks
> Boaz
> 
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

  parent reply	other threads:[~2014-08-27 15:45 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-27 15:22 Boaz Harrosh
2014-08-27 15:25 ` [PATCH 1/5] axonram: Fix bug in direct_access Boaz Harrosh
2014-08-27 15:27 ` [PATCH 2/5] Change direct_access calling convention Boaz Harrosh
2014-08-27 15:28 ` [PATCH 3/5] brd: Add getgeo to block ops Boaz Harrosh
2014-08-27 17:53   ` Matthew Wilcox
2014-08-28  7:26     ` Boaz Harrosh
2014-08-28 15:11       ` Matthew Wilcox
2014-08-28 15:43         ` Boaz Harrosh
2014-08-27 15:30 ` [PATCH 4/5] brd: Fix all partitions BUGs Boaz Harrosh
2014-08-27 15:32 ` [PATCH 5/5] brd: Request from fdisk 4k alignment Boaz Harrosh
2014-08-27 15:45 ` Dmitry Monakhov [this message]
2014-08-27 15:57   ` [PATCHSET 0/5 v2] brd: partition fixes Boaz Harrosh
2014-09-01 10:15 ` Boaz Harrosh
2014-09-09 12:10   ` Boaz Harrosh
2014-09-09 14:25     ` Jens Axboe
2014-09-28 10:45       ` Boaz Harrosh
2014-10-19 17:46       ` Boaz Harrosh
2014-11-04 16:17         ` Boaz Harrosh
2014-11-05  0:50           ` 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=87wq9u7x77.fsf@openvz.org \
    --to=dmonakhov@openvz.org \
    --cc=axboe@fb.com \
    --cc=boaz@plexistor.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ross.zwisler@linux.intel.com \
    --cc=willy@linux.intel.com \
    /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