From: "Theodore Ts'o" <tytso@mit.edu>
To: guan@eryu.me, fstests@vger.kernel.org,
Ext4 Developers List <linux-ext4@vger.kernel.org>,
Eric Whitney <enwlinux@gmail.com>
Subject: Re: [PATCH] ext4/033: test EXT4_IOC_RESIZE_FS by calling the ioctl directly
Date: Wed, 5 Jan 2022 15:02:58 -0500 [thread overview]
Message-ID: <YdX5csi2qZjS1KOt@mit.edu> (raw)
In-Reply-To: <20220105160619.r66lacgq7b7ucyuk@zlang-mailbox>
On Thu, Jan 06, 2022 at 12:06:19AM +0800, Zorro Lang wrote:
> > This patch looks good to me, I just want to ask if we'd better to try to include
> > ext2fs/ext2fs.h at here? And of course, check it in configure.ac.
> > The EXT4_IOC_RESIZE_FS looks like defined in ext2fs/ext2_fs.h which comes from
> > e2fsprogs-devel package. I can't find this definition from kernel-hearders package.
> > As you're the expert of this part, please correct me if it's wrong :)
We're not depending on ext2fs/ext2_fs.h and hence the e2fsprogs-devel
(or libext2fs-dev package if you're using Debian/Ubuntu) anywhere else
in the xfstests-dev. It's not like the code points for
EXT4_IOC_RESIZE_FS are going to change, so we just use constructs
like:
#ifndef EXT4_IOC_RESIZE_FS
#define EXT4_IOC_RESIZE_FS _IOW('f', 16, __u64)
#endif
in xfstests-dev/src/*.c as needed.
There's no real upside in adding a dependency which makes it harder
for developers to compile xfstests. (Trivia note: I created
xfstests-bld several years ago because back then, Debian didn't
include some of the internal header files from xfsprogs which xfstests
needed.)
Cheers,
- Ted
next prev parent reply other threads:[~2022-01-05 20:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Yb9M3aIb9cJGIJaB@desktop>
2021-12-20 20:40 ` [PATCH] ext4/033: test EXT4_IOC_RESIZE_FS by calling the ioctl directly Theodore Ts'o
2022-01-05 15:57 ` Zorro Lang
2022-01-05 16:06 ` Zorro Lang
2022-01-05 20:02 ` Theodore Ts'o [this message]
2022-01-06 2:35 ` Zorro Lang
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=YdX5csi2qZjS1KOt@mit.edu \
--to=tytso@mit.edu \
--cc=enwlinux@gmail.com \
--cc=fstests@vger.kernel.org \
--cc=guan@eryu.me \
--cc=linux-ext4@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;
as well as URLs for NNTP newsgroup(s).