From: Theodore Ts'o <tytso@mit.edu>
To: "Lukáš Czerner" <lczerner@redhat.com>
Cc: Ext4 Developers List <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH 1/3] mke2fs: print a message when creating a regular file
Date: Mon, 5 May 2014 09:52:39 -0400 [thread overview]
Message-ID: <20140505135239.GB22287@thunk.org> (raw)
In-Reply-To: <alpine.LFD.2.00.1405051532280.2223@localhost.localdomain>
On Mon, May 05, 2014 at 03:41:01PM +0200, Lukáš Czerner wrote:
> On Mon, 5 May 2014, Theodore Ts'o wrote:
>
> > Date: Mon, 5 May 2014 09:04:02 -0400
> > From: Theodore Ts'o <tytso@mit.edu>
> > To: Ext4 Developers List <linux-ext4@vger.kernel.org>
> > Cc: Theodore Ts'o <tytso@mit.edu>
> > Subject: [PATCH 1/3] mke2fs: print a message when creating a regular file
>
> Description is missing.
I didn't think more of a description was needed; can you suggest one?
> > /* Can't undo discard ... */
> > - if (!noaction && discard && (io_ptr != undo_io_manager)) {
> > + if (!noaction && discard && dev_size && (io_ptr != undo_io_manager)) {
>
> I wonder whether it's possible not to have dev_size set at this point ?
I checked, and I don't believe so. ext2fs_get_device_size2() never
returns EXT2_ET_UNIMPLEMENTED any more; and it hasn't for quite some
time, since it will use st_size for a regular file or do a binary
search trying to figure out the device size in the worst case. So in
fact, there are some code paths we can eliminate in misc/mke2fs.c
which will simplify this analysis.
Even if there is some case in the future where dev_size could be left
unset, it will be initialized to zero, at which point we will fail
safe by skipping the mke2fs_discard_device() call.
>
> > + if ((fd < 0) && (errno == ENOENT) && (flags & CREATE_FILE)) {
> > + fl |= O_CREAT;
> > + fd = open(device, fl, 0666);
> > + if (fd >= 0 && (flags & VERBOSE_CREATE))
>
> Do we have to use VERBOSE_CREATE ? quiet is global variable so we
> can as well just test that here, or am I missing something ?
The problem is that util.c gets used by both mke2fs.c and tune2fs.c,
and it's only a global variable for mke2fs.c.
My long-term plans is to rename libquota to libsupport, which would
never be built as a shared library, and move some of our various
internal shared utility functions (i.e., e2fsck/profile.c,
misc/util.c, etc.) into that internal e2fsprogs insternal support
library. So in general I'd prefer to minimize the number of global
functions which misc/util.c relies upon.
Cheers,
- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-05-05 13:52 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-05 13:04 [PATCH 1/3] mke2fs: print a message when creating a regular file Theodore Ts'o
2014-05-05 13:04 ` [PATCH 2/3] mke2fs: print extra information about existing ext2/3/4 file systems Theodore Ts'o
2014-05-05 13:45 ` Lukáš Czerner
2014-05-05 14:04 ` Theodore Ts'o
2014-05-05 14:17 ` Lukáš Czerner
2014-05-05 14:28 ` Theodore Ts'o
2014-05-05 14:38 ` Lukáš Czerner
2014-05-05 14:44 ` Theodore Ts'o
2014-05-05 14:51 ` Lukáš Czerner
2014-05-05 14:57 ` Theodore Ts'o
2014-05-05 16:25 ` Andreas Dilger
2014-05-05 17:50 ` Karel Zak
2014-05-05 18:32 ` Theodore Ts'o
2014-05-06 7:44 ` Karel Zak
2014-05-05 16:30 ` Andreas Dilger
2014-05-05 13:04 ` [PATCH 3/3] mke2fs: check for a partition table and warn if present Theodore Ts'o
2014-05-05 13:52 ` Lukáš Czerner
2014-05-05 13:58 ` Theodore Ts'o
2014-05-05 14:11 ` Lukáš Czerner
2014-05-05 14:20 ` Theodore Ts'o
2014-05-06 12:20 ` Karel Zak
2014-05-06 12:52 ` Lukáš Czerner
2014-05-05 13:41 ` [PATCH 1/3] mke2fs: print a message when creating a regular file Lukáš Czerner
2014-05-05 13:52 ` Theodore Ts'o [this message]
2014-05-05 14:04 ` Lukáš Czerner
2014-05-05 14:46 ` Eric Sandeen
2014-05-05 14:49 ` Theodore Ts'o
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=20140505135239.GB22287@thunk.org \
--to=tytso@mit.edu \
--cc=lczerner@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.