From: Dave Chinner <david@fromorbit.com>
To: xfs@oss.sgi.com
Subject: [PATCH 0/2] xfs: extent swap fixes
Date: Thu, 31 Jul 2014 16:12:06 +1000 [thread overview]
Message-ID: <1406787128-11897-1-git-send-email-david@fromorbit.com> (raw)
Hi folks,
The extent swap code is not symmetrical, so correct behaviour is
dependent on userspace doing the right thing. If we try to swap
extents with the temporary inode in the wrong state we can have
interesting failures. These two patches fix those issues and treat
the two files identically in terms of the state of the data
contained in the files being swapped. Failure to write or remove all
cached data from either file will now cause the swap extents
operation to fail.
Comments, thoughts?
Cheers,
Dave.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2014-07-31 6:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-31 6:12 Dave Chinner [this message]
2014-07-31 6:12 ` [PATCH 1/2] xfs: fix swapext ilock deadlock Dave Chinner
2014-07-31 17:15 ` Christoph Hellwig
2014-07-31 6:12 ` [PATCH 2/2] xfs: flush both inodes in xfs_swap_extents Dave Chinner
2014-07-31 17:16 ` Christoph Hellwig
2014-07-31 23:02 ` Dave Chinner
2014-08-01 12:44 ` Brian Foster
2014-08-02 3:19 ` Dave Chinner
2014-08-02 11:24 ` 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=1406787128-11897-1-git-send-email-david@fromorbit.com \
--to=david@fromorbit.com \
--cc=xfs@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox