From: "Darrick J. Wong" <djwong@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: David Chinner <david@fromorbit.com>,
linux-xfs@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: manual merge of the djw-vfs tree with the xfs tree
Date: Tue, 22 Aug 2023 21:46:26 -0700 [thread overview]
Message-ID: <20230823044626.GG11286@frogsfrogsfrogs> (raw)
In-Reply-To: <20230823093347.775f3857@canb.auug.org.au>
On Wed, Aug 23, 2023 at 09:33:47AM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the djw-vfs tree got a conflict in:
>
> fs/xfs/scrub/scrub.c
>
> between commit:
>
> 526aab5f5790 ("xfs: implement online scrubbing of rtsummary info")
>
> from the xfs tree and commit:
>
> ce85a1e04645 ("xfs: stabilize fs summary counters for online fsck")
>
> from the djw-vfs 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.
>
> --
> Cheers,
> Stephen Rothwell
>
> diff --cc fs/xfs/scrub/scrub.c
> index e92129d74462,a0fffbcd022b..000000000000
> --- a/fs/xfs/scrub/scrub.c
> +++ b/fs/xfs/scrub/scrub.c
> @@@ -178,16 -178,16 +178,18 @@@ xchk_teardown
> }
> if (sc->ip) {
> if (sc->ilock_flags)
> - xfs_iunlock(sc->ip, sc->ilock_flags);
> - if (sc->ip != ip_in &&
> - !xfs_internal_inum(sc->mp, sc->ip->i_ino))
> - xchk_irele(sc, sc->ip);
> + xchk_iunlock(sc, sc->ilock_flags);
> + xchk_irele(sc, sc->ip);
> sc->ip = NULL;
> }
> - if (sc->sm->sm_flags & XFS_SCRUB_IFLAG_REPAIR)
> + if (sc->flags & XCHK_HAVE_FREEZE_PROT) {
> + sc->flags &= ~XCHK_HAVE_FREEZE_PROT;
> mnt_drop_write_file(sc->file);
> + }
Yep, I changed the mnt_drop_write_file conditional to be an explicit
flag instead of implied by the XFS_SCRUB_IFLAG_REPAIR coming from
userspace. You've correctly resolved both conflicts, thank you.
(And apologies for things being way messier than is traditional.)
--D
> + if (sc->xfile) {
> + xfile_destroy(sc->xfile);
> + sc->xfile = NULL;
> + }
> if (sc->buf) {
> if (sc->buf_cleanup)
> sc->buf_cleanup(sc->buf);
prev parent reply other threads:[~2023-08-23 4:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 23:33 linux-next: manual merge of the djw-vfs tree with the xfs tree Stephen Rothwell
2023-08-23 4:46 ` Darrick J. Wong [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=20230823044626.GG11286@frogsfrogsfrogs \
--to=djwong@kernel.org \
--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 \
/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