From: Jan Kara <jack@suse.cz>
To: Carlos Maiolino <cmaiolino@redhat.com>
Cc: Theodore Ts'o <tytso@mit.edu>, linux-ext4@vger.kernel.org
Subject: Re: Ext4 developers get-together at the Collab Summit
Date: Fri, 18 Jan 2013 18:27:02 +0100 [thread overview]
Message-ID: <20130118172702.GB18458@quack.suse.cz> (raw)
In-Reply-To: <20130118120626.GB2761@localhost.localdomain>
On Fri 18-01-13 07:06:26, Carlos Maiolino wrote:
> Hi Ted,
>
> I'm not sure yet if I'll be able to go to LSF (need invite), but if I go, I'd
> like to attend Ext4 meeting, and I'd like to bring a discussion about a topic we
> already discussed but didn't go further, about the mount options we
> should/shouldn't support for each filesystem, i.e. today we have some mount
> options that although are not supported for a specific filesystem, it can be
> used to mount that filesystem, one example is mounting ext3 using
> journal_checksum and ext2 with commit=nrsec.
Ah, I think I misunderstood you in your other email so disregard it
please. Discussing whether we should support various mount options when
ext4 driver is used to mount ext2/ext4 indeed makes sence.
> Once we are mostly using ext4 driver to mount ext3 and ext2 fs, I wonder we
> should handle these mount options and deny/warning a mount with
> wrong/non-supported options. Also, I wonder how useful would be to start do
> deprecate ext2/ext3 drivers and just add bugfix to these. Not sure if this is
> already being done, but keeping ext4 as primary ext2/3/4 driver should reduce
> code maintenance and duplication.
ext2/3 already accept mostly bugfixes. And I say mostly because from time
to time I make an exception and accept a well self-contained feature.
FITRIM support was the last example I think. Regarding ext4 being primary -
for Fedora it already is for over an year, right? openSUSE used ext4 to
access ext2 for about an year and 12.3 will use ext4 to access ext3 as well
(unless QA shows some serious issues but I didn't find anything when I
tried it myself). Now I think we can say the transition has completed when
an enterprise distro (RHEL or SLES) switch as well.
Honza
> On Mon, Jan 14, 2013 at 09:48:00AM -0500, Theodore Ts'o wrote:
> > Hi,
> >
> > The Linux Foundation's Collaboration Summit is April 15-17th,
> > and the Linux Storage, File System, and MM Summit is April 18-19th in
> > San Francisco (at the Parc 55 hotel).
> >
> > I'd like to organize an ext4 developer's meeting during the
> > Collab Summit sometime April 15-17th, since so many of us will hopefully
> > be attending LSF. (The CFP will hopefully be coming soon for LSF.)
> >
> > If you're interested in attending, please reply to this thread,
> > and include some suggested topics that you'd be interested in
> > discussing. Based on the number of topics and the number of people who
> > are planning on attending, I'll know how much time we need to reserve
> > and how big of a room to request.
> >
> > Also, if you need a invitation letter for Visa purposes, also
> > please let me know. I can arrange for the Linux Foundation to get that
> > letter sent, so that folks have enough time to get a Visa.
> >
> > Thanks!!
> >
> > - 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
>
> --
> Carlos
> --
> 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
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
prev parent reply other threads:[~2013-01-18 17:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-14 14:48 Ext4 developers get-together at the Collab Summit Theodore Ts'o
2013-01-16 12:01 ` Jan Kara
2013-01-16 16:15 ` Eric Sandeen
2013-01-18 15:39 ` Ric Wheeler
2013-01-18 15:53 ` Carlos Maiolino
2013-01-18 17:14 ` Jan Kara
2013-01-17 13:15 ` Zheng Liu
2013-01-18 8:06 ` Tao Ma
2013-01-18 1:45 ` Zhi Yong Wu
2013-01-18 1:57 ` Zhi Yong Wu
2013-01-18 12:06 ` Carlos Maiolino
2013-01-18 17:27 ` Jan Kara [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=20130118172702.GB18458@quack.suse.cz \
--to=jack@suse.cz \
--cc=cmaiolino@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--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).