linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Besogonov, Aleksei" <cyberax@amazon.com>
To: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>
Cc: Dave Chinner <david@fromorbit.com>
Subject: fallocate on XFS for swap
Date: Fri, 9 Mar 2018 22:05:24 +0000	[thread overview]
Message-ID: <8C28C1CB-47F1-48D1-85C9-5373D29EA13E@amazon.com> (raw)

Hi!

We’re working at Amazon on making XFS our default root filesystem for the upcoming Amazon Linux 2 (now in prod preview). One of the problems that we’ve encountered is inability to use fallocated files for swap on XFS. This is really important for us, since we’re shipping our current Amazon Linux with hibernation support .

I’ve traced the problem to bmap(), used in generic_swapfile_activate call, which returns 0 for blocks inside holes created by fallocate and Dave Chinner confirmed it in a private email. I’m thinking about ways to fix it, so far I see the following possibilities:

1. Change bmap() to not return zeroes for blocks inside holes. But this is an ABI change and it likely will break some obscure userspace utility somewhere.
2. Change generic_swap_activate to use a more modern interface, by adding fiemap-like operation to address_space_operations with fallback on bmap().
3. Add an XFS-specific implementation of swapfile_activate.

What do the people think about it? I kinda like option 2, since it'll make fallocate() work for any other FS that implements fiemap.


             reply	other threads:[~2018-03-09 22:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-09 22:05 Besogonov, Aleksei [this message]
2018-03-09 23:44 ` Darrick J. Wong
2018-03-10  0:58   ` Dave Chinner
2018-03-10  1:17     ` Darrick J. Wong
2018-03-10  1:36       ` Dave Chinner
2018-03-12 22:01         ` Besogonov, Aleksei
2018-03-13  1:31           ` Dave Chinner
2018-03-10  9:38     ` Christoph Hellwig
2018-03-12 21:46       ` Dave Chinner
2018-03-13  7:14         ` Christoph Hellwig
2018-03-12 18:40     ` Besogonov, Aleksei

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=8C28C1CB-47F1-48D1-85C9-5373D29EA13E@amazon.com \
    --to=cyberax@amazon.com \
    --cc=david@fromorbit.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    /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