From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Jan Kara <jack@suse.cz>
Cc: linux-fsdevel@vger.kernel.org,
Christoph Hellwig <hch@infradead.org>,
Matthew Bobrowski <mbobrowski@mbobrowski.org>,
Eric Biggers <ebiggers@kernel.org>
Subject: Re: [PATCH 0/2] iomap: Fix leakage of pipe pages while splicing
Date: Thu, 21 Nov 2019 08:58:29 -0800 [thread overview]
Message-ID: <20191121165829.GK6211@magnolia> (raw)
In-Reply-To: <20191121161144.30802-1-jack@suse.cz>
On Thu, Nov 21, 2019 at 05:15:33PM +0100, Jan Kara wrote:
> Hello,
>
> here is a fix and a cleanup for iomap code. The first patch fixes a leakage
> of pipe pages when iomap_dio_rw() splices to a pipe, the second patch is
> a cleanup that removes strange copying of iter in iomap_dio_rw(). Patches
> have passed fstests for ext4 and xfs and fix the syzkaller reproducer for
> me.
Will have a look, but in the meantime -- do you have quick reproducer
that can be packaged for fstests? Or is it just the syzbot reproducer?
--D
>
> Honza
next prev parent reply other threads:[~2019-11-21 17:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-21 16:15 [PATCH 0/2] iomap: Fix leakage of pipe pages while splicing Jan Kara
2019-11-21 16:15 ` [PATCH 1/2] iomap: Fix pipe page leakage during splicing Jan Kara
2019-11-21 23:55 ` Darrick J. Wong
2019-11-22 6:04 ` Matthew Bobrowski
2019-11-22 10:47 ` Jan Kara
2019-11-22 13:17 ` Christoph Hellwig
2019-11-21 16:15 ` [PATCH 2/2] iomap: Do not create fake iter in iomap_dio_bio_actor() Jan Kara
2019-11-22 0:02 ` Darrick J. Wong
2019-11-22 12:11 ` Jan Kara
2019-11-22 13:26 ` Christoph Hellwig
2019-11-25 8:18 ` Jan Kara
2019-11-21 16:58 ` Darrick J. Wong [this message]
2019-11-21 17:15 ` [PATCH 0/2] iomap: Fix leakage of pipe pages while splicing Jan Kara
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=20191121165829.GK6211@magnolia \
--to=darrick.wong@oracle.com \
--cc=ebiggers@kernel.org \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mbobrowski@mbobrowski.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;
as well as URLs for NNTP newsgroup(s).