linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: David Chinner <david@fromorbit.com>,
	linux-xfs@vger.kernel.org,
	Linux-Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: linux-next: manual merge of the xfs tree with Linus' tree
Date: Thu, 21 Dec 2017 15:01:17 -0800	[thread overview]
Message-ID: <20171221230117.GB12613@magnolia> (raw)
In-Reply-To: <20171222095041.3fe014ec@canb.auug.org.au>

On Fri, Dec 22, 2017 at 09:50:41AM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> Today's linux-next merge of the xfs tree got a conflict in:
> 
>   fs/xfs/xfs_super.c
> 
> between commit:
> 
>   1751e8a6cb93 ("Rename superblock flags (MS_xyz -> SB_xyz)")
> 
> from Linus' tree and commit:
> 
>   10ddf64e420f ("xfs: remove leftover CoW reservations when remounting ro")
> 
> from the xfs tree.
> 
> I fixed it up (see below) and can carry the fix as necessary. This
> is now fixed as far as linux-next is concerned, but any non trivial
> conflicts should be mentioned to your upstream maintainer when your tree
> is submitted for merging.  You may also want to consider cooperating
> with the maintainer of the conflicting tree to minimise any particularly
> complex conflicts.

Ok, that's exactly the merge conflict that I was expecting to see.
I'll make a note if/when I get around to sending a pull request.
Thank you.

--D

> -- 
> Cheers,
> Stephen Rothwell
> 
> diff --cc fs/xfs/xfs_super.c
> index 5122d3021117,2db6a40a96bd..000000000000
> --- a/fs/xfs/xfs_super.c
> +++ b/fs/xfs/xfs_super.c
> @@@ -1368,7 -1369,15 +1369,15 @@@ xfs_fs_remount
>   	}
>   
>   	/* rw -> ro */
>  -	if (!(mp->m_flags & XFS_MOUNT_RDONLY) && (*flags & MS_RDONLY)) {
>  +	if (!(mp->m_flags & XFS_MOUNT_RDONLY) && (*flags & SB_RDONLY)) {
> + 		/* Get rid of any leftover CoW reservations... */
> + 		cancel_delayed_work_sync(&mp->m_cowblocks_work);
> + 		error = xfs_icache_free_cowblocks(mp, NULL);
> + 		if (error) {
> + 			xfs_force_shutdown(mp, SHUTDOWN_CORRUPT_INCORE);
> + 			return error;
> + 		}
> + 
>   		/* Free the per-AG metadata reservation pool. */
>   		error = xfs_fs_unreserve_ag_blocks(mp);
>   		if (error) {
> --
> To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2017-12-21 23:01 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-21 22:50 linux-next: manual merge of the xfs tree with Linus' tree Stephen Rothwell
2017-12-21 23:01 ` Darrick J. Wong [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-10-31  0:41 Stephen Rothwell
2022-03-30 22:00 Stephen Rothwell
2022-01-17 22:30 Stephen Rothwell
2022-01-18 18:17 ` Darrick J. Wong
2019-07-16 23:36 Stephen Rothwell
2018-10-31  0:22 Stephen Rothwell
2018-10-31  1:05 ` Dave Chinner
2018-06-05  0:34 Stephen Rothwell
2018-06-05  0:38 ` Stephen Rothwell
2018-06-05  0:59 ` Dave Chinner
2018-06-05  1:13   ` Andreas Grünbacher
2018-06-05  1:25   ` Stephen Rothwell
2016-07-21  1:07 Stephen Rothwell
2016-07-21  1:35 ` Dave Chinner
2015-04-20  2:24 Stephen Rothwell
2012-01-03  1:06 Stephen Rothwell
2012-01-03  1:34 ` Dave Chinner
2011-09-15  2:30 Stephen Rothwell
2011-09-15 11:05 ` Christoph Hellwig
2011-03-28  1:21 Stephen Rothwell
2009-08-18  0:12 Stephen Rothwell
2009-08-18  6:49 ` Felix Blyakher
2009-08-18  7:17   ` 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=20171221230117.GB12613@magnolia \
    --to=darrick.wong@oracle.com \
    --cc=david@fromorbit.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=torvalds@linux-foundation.org \
    --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).