From: Christoph Hellwig <hch@infradead.org>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Dave Chinner <david@fromorbit.com>,
linux-xfs@vger.kernel.org, git.user@gmail.com
Subject: Re: [PATCH] xfs: fix transaction leak in xfs_reflink_allocate_cow()
Date: Mon, 17 Sep 2018 09:30:56 -0700 [thread overview]
Message-ID: <20180917163056.GA11440@infradead.org> (raw)
In-Reply-To: <20180917162912.GC4607@magnolia>
On Mon, Sep 17, 2018 at 09:29:12AM -0700, Darrick J. Wong wrote:
> > +find_trim_cow_extent(
>
> /me prefers that we try to prefix all the xfs functions, even if they
> are static...
Heh, I actually just did that. I have a series that starts with this
respin that I plan to post later today.
prev parent reply other threads:[~2018-09-17 21:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-07 1:51 [PATCH] xfs: fix transaction leak in xfs_reflink_allocate_cow() Dave Chinner
2018-09-07 2:40 ` Darrick J. Wong
2018-09-07 13:11 ` Alexander Y. Fomichev
2018-09-07 14:03 ` Brian Foster
2018-09-10 7:02 ` Christoph Hellwig
2018-09-12 9:24 ` Alexander Y. Fomichev
2018-09-17 16:29 ` Darrick J. Wong
2018-09-17 16:30 ` 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=20180917163056.GA11440@infradead.org \
--to=hch@infradead.org \
--cc=darrick.wong@oracle.com \
--cc=david@fromorbit.com \
--cc=git.user@gmail.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;
as well as URLs for NNTP newsgroup(s).