From: Djalal Harouni <tixxdz@opendz.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Al Viro <viro@ZenIV.linux.org.uk>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Theodore Ts'o <tytso@mit.edu>, Jan Kara <jack@suse.cz>
Subject: Re: linux-next: manual merge of the vfs tree with the ext4 tree
Date: Fri, 6 Jan 2012 21:46:01 +0100 [thread overview]
Message-ID: <20120106204601.GA26305@dztty> (raw)
In-Reply-To: <20120106135442.1720766a6c1510abf51b2aff@canb.auug.org.au>
Hello,
(Cc'ed Jan Kara).
On Fri, Jan 06, 2012 at 01:54:42PM +1100, Stephen Rothwell wrote:
> Hi Al,
>
> Today's linux-next merge of the vfs tree got a conflict in
> fs/ext4/ioctl.c between commits 2a415f129806 ("ext4: add missing
> ext4_resize_end on error paths") and 22cdfca56418 ("ext4: remove unneeded
> file_remove_suid() from ext4_ioctl()") from the ext4 tree and commit
There is also another commit from ext4 involved:
commit ce06c5fa14f1a ("ext{3,4}: Fix potential race when setversion ioctl
updates inode) by Jan Kara.
All these ext4 commits are fine.
> a561be7100cd ("switch a bunch of places to mnt_want_write_file()") from
> the vfs tree.
>
> I fixed it up (see below) and can carry the fix as necessary.
> --
> Cheers,
> Stephen Rothwell sfr@canb.auug.org.au
>
> diff --cc fs/ext4/ioctl.c
> index f2c335b,d37b3bb..0000000
> --- a/fs/ext4/ioctl.c
> +++ b/fs/ext4/ioctl.c
> @@@ -173,11 -170,8 +173,11 @@@ flags_out
> err = ext4_mark_iloc_dirty(handle, inode, &iloc);
> }
> ext4_journal_stop(handle);
> +
> +unlock_out:
> + mutex_unlock(&inode->i_mutex);
This is the code related to commit: ce06c5fa14f1a
Thanks for the fix.
> setversion_out:
> - mnt_drop_write(filp->f_path.mnt);
> + mnt_drop_write_file(filp);
> return err;
> }
> case EXT4_IOC_GROUP_EXTEND: {
> @@@ -197,13 -189,12 +197,13 @@@
> EXT4_FEATURE_RO_COMPAT_BIGALLOC)) {
> ext4_msg(sb, KERN_ERR,
> "Online resizing not supported with bigalloc");
> - return -EOPNOTSUPP;
> + err = -EOPNOTSUPP;
> + goto group_extend_out;
> }
>
> - err = mnt_want_write(filp->f_path.mnt);
> + err = mnt_want_write_file(filp);
> if (err)
> - return err;
> + goto group_extend_out;
>
> err = ext4_group_extend(sb, EXT4_SB(sb)->s_es, n_blocks_count);
> if (EXT4_SB(sb)->s_journal) {
> @@@ -213,10 -204,9 +213,10 @@@
> }
> if (err == 0)
> err = err2;
> +
> - mnt_drop_write(filp->f_path.mnt);
> + mnt_drop_write_file(filp);
> +group_extend_out:
> ext4_resize_end(sb);
> -
> return err;
> }
>
> @@@ -256,7 -246,9 +256,7 @@@
>
> err = ext4_move_extents(filp, donor_filp, me.orig_start,
> me.donor_start, me.len, &me.moved_len);
> - mnt_drop_write(filp->f_path.mnt);
> + mnt_drop_write_file(filp);
> - if (me.moved_len > 0)
> - file_remove_suid(donor_filp);
>
> if (copy_to_user((struct move_extent __user *)arg,
> &me, sizeof(me)))
> @@@ -284,13 -274,12 +284,13 @@@ mext_out
> EXT4_FEATURE_RO_COMPAT_BIGALLOC)) {
> ext4_msg(sb, KERN_ERR,
> "Online resizing not supported with bigalloc");
> - return -EOPNOTSUPP;
> + err = -EOPNOTSUPP;
> + goto group_add_out;
> }
>
> - err = mnt_want_write(filp->f_path.mnt);
> + err = mnt_want_write_file(filp);
> if (err)
> - return err;
> + goto group_add_out;
>
> err = ext4_group_add(sb, &input);
> if (EXT4_SB(sb)->s_journal) {
> @@@ -300,10 -289,9 +300,10 @@@
> }
> if (err == 0)
> err = err2;
> +
> - mnt_drop_write(filp->f_path.mnt);
> + mnt_drop_write_file(filp);
> +group_add_out:
> ext4_resize_end(sb);
> -
> return err;
> }
>
--
tixxdz
http://opendz.org
next prev parent reply other threads:[~2012-01-06 20:46 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-06 2:54 linux-next: manual merge of the vfs tree with the ext4 tree Stephen Rothwell
2012-01-06 20:46 ` Djalal Harouni [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-01-27 22:51 Stephen Rothwell
2016-05-17 0:23 Stephen Rothwell
2016-05-17 3:16 ` Theodore Ts'o
2016-05-18 14:25 ` Arnd Bergmann
2016-05-19 1:26 ` Stephen Rothwell
2015-06-09 2:47 Stephen Rothwell
2015-05-11 0:49 Stephen Rothwell
2015-04-15 1:35 Stephen Rothwell
2015-04-14 1:30 Stephen Rothwell
2015-04-14 1:48 ` Al Viro
2015-04-14 17:00 ` Theodore Ts'o
2015-04-14 17:17 ` Al Viro
2015-04-14 21:02 ` Theodore Ts'o
2015-04-14 21:14 ` Al Viro
2015-04-13 1:48 Stephen Rothwell
2015-04-13 1:43 Stephen Rothwell
2015-04-07 4:00 Stephen Rothwell
2015-04-07 7:02 ` Christoph Hellwig
2015-04-07 7:36 ` Stephen Rothwell
2015-04-08 3:26 ` Theodore Ts'o
2015-04-14 16:18 ` Christoph Hellwig
2015-04-14 20:43 ` Theodore Ts'o
2014-05-27 2:07 Stephen Rothwell
2014-04-22 1:13 Stephen Rothwell
2011-12-21 0:18 Stephen Rothwell
2011-12-21 0:43 ` Stephen Rothwell
2011-07-18 3:36 Stephen Rothwell
2011-07-25 2:38 ` Stephen Rothwell
2009-05-19 4:23 Stephen Rothwell
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=20120106204601.GA26305@dztty \
--to=tixxdz@opendz.org \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=tytso@mit.edu \
--cc=viro@ZenIV.linux.org.uk \
/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).