From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Omar Sandoval <osandov@osandov.com>
Cc: linux-xfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Jan Kara <jack@suse.cz>, Christoph Hellwig <hch@infradead.org>,
Aleksei Besogonov <cyberax@amazon.com>,
kernel-team@fb.com
Subject: Re: [PATCH v3 0/2] iomap: swapfile tweaks
Date: Thu, 17 May 2018 10:23:55 -0700 [thread overview]
Message-ID: <20180517172355.GS23858@magnolia> (raw)
In-Reply-To: <cover.1526493125.git.osandov@fb.com>
On Wed, May 16, 2018 at 10:54:09AM -0700, Omar Sandoval wrote:
> From: Omar Sandoval <osandov@fb.com>
>
> Changes from v2:
>
> - Move up inline flag check, which Christoph is going to turn into a
> type at some point
> - Remove null address check, since it doesn't make sense for
> IOMAP_MAPPED or IOMAP_UNWRITTEN
>
> Omar Sandoval (2):
> iomap: provide more useful errors for invalid swap files
> iomap: don't allow holes in swapfiles
>
> fs/iomap.c | 43 +++++++++++++++++++++++--------------------
Tested ok overnight, so:
Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com>
--D
> 1 file changed, 23 insertions(+), 20 deletions(-)
>
> --
> 2.17.0
>
> --
> 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
prev parent reply other threads:[~2018-05-17 17:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-16 17:54 [PATCH v3 0/2] iomap: swapfile tweaks Omar Sandoval
2018-05-16 17:54 ` [PATCH v3 1/2] iomap: provide more useful errors for invalid swap files Omar Sandoval
2018-05-16 18:10 ` Christoph Hellwig
2018-05-17 8:58 ` Jan Kara
2018-05-16 17:54 ` [PATCH v3 2/2] iomap: don't allow holes in swapfiles Omar Sandoval
2018-05-16 18:11 ` Christoph Hellwig
2018-05-17 8:59 ` Jan Kara
2018-05-17 17:23 ` 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=20180517172355.GS23858@magnolia \
--to=darrick.wong@oracle.com \
--cc=cyberax@amazon.com \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--cc=kernel-team@fb.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=osandov@osandov.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;
as well as URLs for NNTP newsgroup(s).