From: Mike Snitzer <snitzer@redhat.com>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: device-mapper development <dm-devel@redhat.com>,
"Alasdair G. Kergon" <agk@redhat.com>
Subject: Re: [PATCH v2] dm: Fix alignment stacking on partitioned devices
Date: Fri, 8 Jan 2010 15:28:07 -0500 [thread overview]
Message-ID: <20100108202807.GA21439@redhat.com> (raw)
In-Reply-To: <yq13a2gsal8.fsf@sermon.lab.mkp.net>
On Fri, Jan 08 2010 at 1:41pm -0500,
Martin K. Petersen <martin.petersen@oracle.com> wrote:
> >>>>> "Mike" == Mike Snitzer <snitzer@redhat.com> writes:
>
> Mike,
>
> Mike> Seems I took the time to add a comment whose FIXME doesn't ring
> Mike> many bells now! But ignoring that, the comment before the FIXME
> Mike> is making a veiled reference to userspace having consumed
> Mike> alignment_offset.
>
> I read and understood the comment. But even then explicitly zeroing out
> those two values didn't make sense (because if user space did in fact do
> the right thing they'd always be zero).
>
> I know that the DM utilities take care of business. And that DM devices
> are special because they are always set up by user space and not a
> kernel discovery process.
>
> But since the code *is* in place to validate things I'm not so keen on
> you clearing fields that have been calculated and have a meaning. For
> me it masked a case where the DM utilities did the wrong thing (because
> they were old).
>
> With the Enterprise Linux hat on it is easy for us to specify that you
> must use this version of the kernel and the device mapper utilities.
> But reality is that lots of people are running upstream kernels on
> distributions with older userland. And some distributions get things
> wrong, ship broken bits, etc.
>
> It's great that new DM utils will transparently adjust the starting
> offset. That's the way it's supposed to work. No arguments there.
>
> My main concern is making sure that we never get into a case where we
> run with misaligned components without indicating that there is a
> problem. Ever! Regardless of which DM utils might be in place.
>
> We have the power to get that right. All the pieces are in place. I'd
> simply like us to stop making assumptions about user space always doing
> the right thing.
Yeap, I already agreed that those 2 lines should be removed (in the
p.s. of my previous mail). They really aren't serving any purpose and
their justification was/is tenuous at best.
I'll get the fix, for 2.6.33, to Alasdair shortly.
Mike
next prev parent reply other threads:[~2010-01-08 20:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-23 18:07 [PATCH v2] dm: Fix alignment stacking on partitioned devices Mike Snitzer
2009-12-23 19:21 ` Mike Snitzer
2010-01-05 18:04 ` Alasdair G Kergon
2010-01-05 18:27 ` Alasdair G Kergon
2010-01-06 2:23 ` Martin K. Petersen
2010-01-06 2:57 ` Mike Snitzer
2010-01-06 3:03 ` Mike Snitzer
2010-01-06 3:24 ` Martin K. Petersen
2010-01-06 4:10 ` Mike Snitzer
2010-01-06 4:16 ` Martin K. Petersen
2010-01-06 5:16 ` Mike Snitzer
2010-01-06 8:39 ` Martin K. Petersen
2010-01-06 13:25 ` Mike Snitzer
2010-01-07 17:15 ` Martin K. Petersen
2010-01-07 18:55 ` Mike Snitzer
2010-01-08 18:41 ` Martin K. Petersen
2010-01-08 20:28 ` Mike Snitzer [this message]
2010-01-09 0:01 ` [PATCH] block: bdev_stack_limits wrapper and DM topology fixes Mike Snitzer
2010-01-06 13:55 ` [PATCH v2] dm: Fix alignment stacking on partitioned devices Alasdair G Kergon
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=20100108202807.GA21439@redhat.com \
--to=snitzer@redhat.com \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=martin.petersen@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.