linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 0/4] Clean up ext4's mount option parsing code
Date: Sat,  2 Feb 2013 23:44:02 -0500	[thread overview]
Message-ID: <1359866646-29876-1-git-send-email-tytso@mit.edu> (raw)

The first three patches are from a patch series which Jan Kara submitted
back in April 2012, forward ported to modern kernels.  The last patch
addresses the feature which Carlos suggested, but I've implemented it as
a flag in the mount options parsing, instead of using the mount option
flags.  This allows us to disallow features which don't involve setting
a mount option flags.

						- Ted

Jan Kara (3):
  ext4: move several mount options to standard handling loop
  ext4: make mount option parsing loop more logical
  ext4: print error when argument of inode_readahead_blk is invalid

Theodore Ts'o (1):
  ext4: check incompatible mount options while mounting ext2/3

 fs/ext4/super.c | 261 +++++++++++++++++++++++++++++++-------------------------
 1 file changed, 143 insertions(+), 118 deletions(-)

-- 
1.7.12.rc0.22.gcdd159b


             reply	other threads:[~2013-02-03  4:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-03  4:44 Theodore Ts'o [this message]
2013-02-03  4:44 ` [PATCH 1/4] ext4: move several mount options to standard handling loop Theodore Ts'o
2013-02-03  4:44 ` [PATCH 2/4] ext4: make mount option parsing loop more logical Theodore Ts'o
2013-02-03  4:44 ` [PATCH 3/4] ext4: print error when argument of inode_readahead_blk is invalid Theodore Ts'o
2013-02-03  4:44 ` [PATCH 4/4] ext4: check incompatible mount options while mounting ext2/3 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=1359866646-29876-1-git-send-email-tytso@mit.edu \
    --to=tytso@mit.edu \
    --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).