From: Chris Mason <chris.mason@oracle.com>
To: linux-btrfs@vger.kernel.org
Subject: New ioctl API pushed out
Date: Fri, 16 Jan 2009 12:38:59 -0500 [thread overview]
Message-ID: <1232127539.21473.64.camel@think.oraclecorp.com> (raw)
Hello everyone,
I had said that a revision of the ioctl API wouldn't be required and
that I'd maintain compatibility even for my simple ioctl calls now.
But, Ryusuke Konishi noticed that I didn't align the ioctl argument
properly and that it was actually different sizes on 32 bit and 64 bit
compiles.
In general, the kernel has a compat ioctl facility to deal with this,
letting us use different code to deal with a 32 bit executable run on 64
bit machines.
But, it is a lot of cruft to carry around for a structure that is 1 byte
off. I think it is better for the project if I just change the arg now
and release v0.18 of btrfs-progs
I've asked Linus to pull these ioctl changes, and so v2.6.29-rc2 will
require v0.18 of btrfs-progs for the ioctl commands.
The disk format has not changed. Any filesystems created by v0.17 and
2.6.29-rc1 will still be usable. The commands to scan devices, add,
remove and balance volumes use these ioctls. You will need to update
your btrfs-progs if you plan on using those commands in 2.6.29-rc2
Sorry for the trouble on this one, I really should have caught this
simple error.
-chris
reply other threads:[~2009-01-16 17:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1232127539.21473.64.camel@think.oraclecorp.com \
--to=chris.mason@oracle.com \
--cc=linux-btrfs@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