From: Andrew Morton <akpm@osdl.org>
To: "Darrick J. Wong" <djwong@us.ibm.com>
Cc: dm-devel@redhat.com, lcm@us.ibm.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] User-configurable HDIO_GETGEO for dm volumes
Date: Thu, 16 Feb 2006 17:49:51 -0800 [thread overview]
Message-ID: <20060216174951.22b50ded.akpm@osdl.org> (raw)
In-Reply-To: <43F5275A.6070603@us.ibm.com>
"Darrick J. Wong" <djwong@us.ibm.com> wrote:
>
> ...
> > That's brave - we take the hd_geometry straight from userspace without
> > checking anything?
>
> My original approach didn't work anyway; libdevmapper thinks that a
> target message is a string and would stop copying at the first null it
> saw. Since you're also concerned about being locked into a particular
> hd_geometry structure layout, I respun the patch so that dmsetup passes
> a string to the dm configuration code; now dm performs some basic
> range/sanity checks. However, the patch doesn't check that the CHS
> values make sense or are even close to the real disk size; if somebody
> in userspace wants to configure a 150G dm device to have the same
> geometry as a 360K floppy disk, so be it. Geometries seem to be rather
> inaccurate anyway.
>
> Or, were you worried that I'm dereferencing a userspace pointer in the
> kernel? The code that calls _setgeo handles that properly.
Well, I was just asking whether you'd thought about it...
> > Will this code dtrt if userspace is 32-bit and the kernel is 64-bit?
>
> There shouldn't be any 32/64 mis-match issues with passing a string. If
> one tries to pass too-large values, -EINVAL is returned.
Yup, strings work.
> > > struct hd_geometry looks like something which different compilers could lay
> > out differently, perhaps even different gcc versions. We're relying upon
> > the userspace representation being identical to the kernel's
> > representation.
> >
> > It means that struct hd_geometry becomes part of the kernel ABI. We can
> > never again change it and neither we (nor the compiler) can ever change its
> > layout. That's dangerous. I'd suggest that you not use hd_geometry in
> > this way (unless we're already using it that way, which might be the case).
>
> hd_geometry is already part of the kernel ABI because the HDIO_GETGEO
> ioctl takes a pointer to a struct hd_geometry in userspace and fills it
> out.
argh.
>
> Signed-off-by: Darrick J. Wong <djwong@us.ibm.com>
>
We don't seem to have a changelog any more.
next prev parent reply other threads:[~2006-02-17 1:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-15 20:22 Darrick J. Wong
2006-02-16 3:05 ` Andrew Morton
2006-02-17 1:31 ` Darrick J. Wong
2006-02-17 1:49 ` Andrew Morton [this message]
2006-02-17 15:16 ` Alasdair G Kergon
2006-02-17 15:21 ` [dm-devel] " Alasdair G Kergon
2006-02-18 0:59 ` Darrick J. Wong
2006-02-19 1:25 ` [dm-devel] " Alasdair G Kergon
2006-02-22 22:32 ` Alasdair G Kergon
2006-02-23 0:46 ` Darrick J. Wong
2006-02-23 13:56 ` Alasdair G Kergon
2006-02-23 18:16 ` Darrick J. Wong
2006-02-17 8:14 Seewer Philippe
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=20060216174951.22b50ded.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=djwong@us.ibm.com \
--cc=dm-devel@redhat.com \
--cc=lcm@us.ibm.com \
--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