All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Brian Foster <bfoster@redhat.com>
Cc: kaixuxia <xiakaixu1987@gmail.com>,
	linux-xfs@vger.kernel.org,
	"Darrick J. Wong" <darrick.wong@oracle.com>,
	newtongao@tencent.com, jasperwang@tencent.com
Subject: Re: [PATCH V2] xfs: Fix agi&agf ABBA deadlock when performing rename with RENAME_WHITEOUT flag
Date: Tue, 20 Aug 2019 21:23:04 +1000	[thread overview]
Message-ID: <20190820112304.GF1119@dread.disaster.area> (raw)
In-Reply-To: <20190820105101.GA14307@bfoster>

On Tue, Aug 20, 2019 at 06:51:01AM -0400, Brian Foster wrote:
> On Tue, Aug 20, 2019 at 04:53:22PM +0800, kaixuxia wrote:
> FWIW if we do take that approach, then IMO it's worth reconsidering the
> 1-2 liner I originally proposed to fix the locking. It's slightly hacky,
> but really all three options are hacky in slightly different ways. The
> flipside is it's trivial to implement, review and backport and now would
> be removed shortly thereafter when we replace the on-disk whiteout with
> the in-core fake whiteout thing. Just my .02 though..

We've got to keep the existing whiteout method around for,
essentially, forever, because we have to support kernels that don't
do in-memory translations of DT_WHT to a magic chardev inode and
vice versa (i.e. via mknod). IOWs, we'll need a feature bit to
indicate that we actually have DT_WHT based whiteouts on disk.

So we may as well fix this properly now by restructuring the code as
we will still have to maintain this functionality for a long time to
come.

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

  reply	other threads:[~2019-08-20 11:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-19 13:06 [PATCH V2] xfs: Fix agi&agf ABBA deadlock when performing rename with RENAME_WHITEOUT flag kaixuxia
2019-08-19 15:13 ` Brian Foster
2019-08-19 22:12   ` Dave Chinner
2019-08-20  6:45   ` kaixuxia
2019-08-20  8:07     ` Dave Chinner
2019-08-20  8:53       ` kaixuxia
2019-08-20 10:51         ` Brian Foster
2019-08-20 11:23           ` Dave Chinner [this message]
2019-08-20 12:23             ` Brian Foster
2019-08-20 22:13               ` Dave Chinner
2019-08-21 11:25                 ` Brian Foster

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=20190820112304.GF1119@dread.disaster.area \
    --to=david@fromorbit.com \
    --cc=bfoster@redhat.com \
    --cc=darrick.wong@oracle.com \
    --cc=jasperwang@tencent.com \
    --cc=linux-xfs@vger.kernel.org \
    --cc=newtongao@tencent.com \
    --cc=xiakaixu1987@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.