public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: Christoph Hellwig <hch@lst.de>,
	linux-xfs@vger.kernel.org, bfoster@redhat.com
Subject: Re: [PATCH v3] xfs: open code end_buffer_async_write in xfs_finish_page_writeback
Date: Sat, 2 Sep 2017 18:32:45 +0200	[thread overview]
Message-ID: <20170902163245.GA6141@lst.de> (raw)
In-Reply-To: <20170816154454.GX4796@magnolia>

On Wed, Aug 16, 2017 at 08:44:54AM -0700, Darrick J. Wong wrote:
> On Wed, Aug 16, 2017 at 10:51:57AM +0200, Christoph Hellwig wrote:
> > Our loop in xfs_finish_page_writeback, which iterates over all buffer
> > heads in a page and then calls end_buffer_async_write, which also
> > iterates over all buffers in the page to check if any I/O is in flight
> > is not only inefficient, but also potentially dangerous as
> > end_buffer_async_write can cause the page and all buffers to be freed.
> > 
> > Replace it with a single loop that does the work of end_buffer_async_write
> > on a per-page basis.
> > 
> > Signed-off-by: Christoph Hellwig <hch@lst.de>
> 
> Looks ok,
> Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com>
> 
> I'm assuming 4.14 for this one, unless you know of people banging into
> use-after-free problems and therefore need it pushed into 4.13?

Looks like it didn't make it into for-next for 4.14 either.

  parent reply	other threads:[~2017-09-02 16:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-16  8:51 [PATCH v3] xfs: open code end_buffer_async_write in xfs_finish_page_writeback Christoph Hellwig
2017-08-16 11:57 ` Brian Foster
2017-08-16 15:44 ` Darrick J. Wong
2017-08-17  7:37   ` Christoph Hellwig
2017-09-02 16:32   ` Christoph Hellwig [this message]
2017-09-02 17:08     ` Darrick J. Wong

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=20170902163245.GA6141@lst.de \
    --to=hch@lst.de \
    --cc=bfoster@redhat.com \
    --cc=darrick.wong@oracle.com \
    --cc=linux-xfs@vger.kernel.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