From: Christoph Hellwig <hch@infradead.org>
To: David Chinner <dgc@sgi.com>
Cc: xfs-dev <xfs-dev@sgi.com>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: review: fix use after free of log buffers on shutdown.
Date: Mon, 23 Apr 2007 22:24:03 +0100 [thread overview]
Message-ID: <20070423212403.GD13572@infradead.org> (raw)
In-Reply-To: <20070419075338.GV48531920@melbourne.sgi.com>
On Thu, Apr 19, 2007 at 05:53:38PM +1000, David Chinner wrote:
>
> When unmounting the filesystem we write an unmount record into the
> log just before we start freeing up in memory structures.
>
> When we wait for the unmount record to hit the disk, we don't
> wait for the log buffers to be finished with, we only wait for part of
> the iodone callback to be run - the bit that processes the
> unmount record completion.
>
> Hence when the unmount wakes up, it races with the remainder of the
> log io completion and pretty much the first thing it does is free
> the log buffers.
>
> As a result, when iodone processing completes and we check the
> buffer's async status, the buffer can already have been freed.
>
> Luckily, all log I/O is issued asynchronously, so we don't really
> need the async check and so we can avoid this use after free
> easily.
Looks good to me.
> Index: 2.6.x-xfs-new/fs/xfs/xfs_log.c
> ===================================================================
> --- 2.6.x-xfs-new.orig/fs/xfs/xfs_log.c 2007-04-19 17:18:14.097380099 +1000
> +++ 2.6.x-xfs-new/fs/xfs/xfs_log.c 2007-04-19 17:51:03.017078512 +1000
> @@ -988,14 +988,16 @@ xlog_iodone(xfs_buf_t *bp)
> } else if (iclog->ic_state & XLOG_STATE_IOERROR) {
> aborted = XFS_LI_ABORTED;
> }
> +
> + /* log I/O is always issued ASYNC */
> + ASSERT(XFS_BUF_ISASYNC(bp));
> xlog_state_done_syncing(iclog, aborted);
> - if (!(XFS_BUF_ISASYNC(bp))) {
> - /*
> - * Corresponding psema() will be done in bwrite(). If we don't
> - * vsema() here, panic.
> - */
> - XFS_BUF_V_IODONESEMA(bp);
> - }
> + /*
> + * do not reference the buffer (bp) here as we could race
> + * with it being freed after writing the unmount record to the
> + * log.
> + */
> +
> } /* xlog_iodone */
>
> /*
>
>
---end quoted text---
prev parent reply other threads:[~2007-04-23 21:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-19 7:53 review: fix use after free of log buffers on shutdown David Chinner
2007-04-23 21:24 ` Christoph Hellwig [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=20070423212403.GD13572@infradead.org \
--to=hch@infradead.org \
--cc=dgc@sgi.com \
--cc=xfs-dev@sgi.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