From: Phillip Susi <psusi@ubuntu.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: "Dr. Tilmann Bubeck" <t.bubeck@reinform.de>, linux-ext4@vger.kernel.org
Subject: Re: Use EXT4_BOOT_LOADER_INO for boot loader GRUB?
Date: Tue, 05 Feb 2013 21:15:40 -0500 [thread overview]
Message-ID: <5111BCCC.70709@ubuntu.com> (raw)
In-Reply-To: <20130126184927.GB20005@thunk.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 01/26/2013 01:49 PM, Theodore Ts'o wrote:
> What I'm thinking about is a new ioctl that would swap the i_block
> and i_blocks array of the BOOT_LOADER_INO and the file descriptor.
> That is, if there were any blocks attached to the boot_loader_ino,
> they would become attached to the inode associated with the file
> descriptor, and the blocks associated with that inode would be
> attached to inode #5.
Isn't that what the new defrag ioctl does already? So you just need a
way to open the reserved and unnamed inode to call the ioctl on.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/
iQEcBAEBAgAGBQJREbzMAAoJEJrBOlT6nu75KrwH/1tMG3rGEsXpIt61kPQDkH77
QDquiA31N57c8DxPVc8/ibZdNhCAjH84TZFW3Lopzr6zCh03ZbOs08AsEyDeXvWw
pTp3mJzmLvI1Lq7x6snYEA3ndd/taswo9bZwf2fwUwi2hQIBux+G65gnFECiybms
EV4zwUJSVtF8l77HTidrUODQgnI9j+MMwKILWtsgoBsGjMX5eHSO/5fgMCfnIvcv
q5MIU7V0JjaQVMTSAPOVXcy3ZAnvHv2rt+JNX5UyA1bST7BKd/uF9GQAxkakfLnH
oGeYzN9bRayGCszlcIeUMv0xv7J3KXFNB/MpKx42zlPyps92boThv1jLnkWrgOg=
=8PlP
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2013-02-06 2:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-25 8:18 Use EXT4_BOOT_LOADER_INO for boot loader GRUB? Dr. Tilmann Bubeck
2013-01-26 18:49 ` Theodore Ts'o
2013-02-06 2:15 ` Phillip Susi [this message]
2013-02-19 21:15 ` Dr. Tilmann Bubeck
2013-03-18 13:26 ` Dr. Tilmann Bubeck
2013-03-18 13:51 ` Theodore Ts'o
2013-04-07 2:47 ` [PATCH -v3] ext4: implementation of a new ioctl called EXT4_IOC_SWAP_BOOT Theodore Ts'o
2013-04-07 17:09 ` Andreas Dilger
2013-04-07 19:48 ` Theodore Ts'o
2013-04-07 21:29 ` Andreas Dilger
2013-04-07 18:43 ` Dr. Tilmann Bubeck
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=5111BCCC.70709@ubuntu.com \
--to=psusi@ubuntu.com \
--cc=linux-ext4@vger.kernel.org \
--cc=t.bubeck@reinform.de \
--cc=tytso@mit.edu \
/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;
as well as URLs for NNTP newsgroup(s).