From: "David S. Miller" <davem@redhat.com>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: BLKGETSIZE64 is broken (0x80041272)
Date: 27 Mar 2003 23:42:49 -0800 [thread overview]
Message-ID: <1048837368.22744.0.camel@rth.ninka.net> (raw)
In-Reply-To: <20030327214214.B19517@devserv.devel.redhat.com>
On Thu, 2003-03-27 at 18:42, Pete Zaitcev wrote:
> I was adding ioctl translations and found that BLKGETSIZE64
> equals 0x80041272, with wrong size. Apparently, a whole bunch
> of ioctls takes sizeof(sizeof(foo)), which evaluates to 4
> in 32 bit userland, regardless of the size of foo.
> Are we going to do anything about it?
Anton and I noticed this a few months ago, we just handle it
the way it needs to be in the ioctl32 translation layers of
ppc64 and sparc64. I believe we even notified people such
as Andi Kleen at the time this was discovered by Anton.
--
David S. Miller <davem@redhat.com>
prev parent reply other threads:[~2003-03-28 7:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-28 2:42 Pete Zaitcev
2003-03-28 3:55 ` Anton Blanchard
2003-03-28 7:42 ` David S. Miller [this message]
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=1048837368.22744.0.camel@rth.ninka.net \
--to=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zaitcev@redhat.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
all inboxes | Powered by JetHome®