From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: "Luis R. Rodriguez" <mcgrof@kernel.org>
Cc: xfs <linux-xfs@vger.kernel.org>
Subject: Re: [PATCH] xfs: always free inline data before resetting inode fork during ifree
Date: Thu, 22 Mar 2018 20:41:45 -0700 [thread overview]
Message-ID: <20180323034145.GH4818@magnolia> (raw)
In-Reply-To: <20180323013037.GA9190@wotan.suse.de>
On Fri, Mar 23, 2018 at 01:30:37AM +0000, Luis R. Rodriguez wrote:
> On Wed, Nov 22, 2017 at 10:01:37PM -0800, Darrick J. Wong wrote:
> > From: Darrick J. Wong <darrick.wong@oracle.com>
> >
> > In xfs_ifree, we reset the data/attr forks to extents format without
> > bothering to free any inline data buffer that might still be around
> > after all the blocks have been truncated off the file. Prior to commit
> > 43518812d2 ("xfs: remove support for inlining data/extents into the
> > inode fork") nobody noticed because the leftover inline data after
> > truncation was small enough to fit inside the inline buffer inside the
> > fork itself.
> >
> > However, now that we've removed the inline buffer, we /always/ have to
> > free the inline data buffer or else we leak them like crazy. This test
> > was found by turning on kmemleak for generic/001 or generic/388.
> >
> > Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
> > ---
> > fs/xfs/xfs_inode.c | 21 +++++++++++++++++++++
> > 1 file changed, 21 insertions(+)
> >
> > diff --git a/fs/xfs/xfs_inode.c b/fs/xfs/xfs_inode.c
> > index 61d1cb7..8012741 100644
> > --- a/fs/xfs/xfs_inode.c
> > +++ b/fs/xfs/xfs_inode.c
> > @@ -2401,6 +2401,24 @@ xfs_ifree_cluster(
> > }
> >
> > /*
> > + * Free any local-format buffers sitting around before we reset to
> > + * extents format.
> > + */
> > +static inline void
> > +xfs_ifree_local_data(
> > + struct xfs_inode *ip,
> > + int whichfork)
> > +{
> > + struct xfs_ifork *ifp;
> > +
> > + if (XFS_IFORK_FORMAT(ip, whichfork) != XFS_DINODE_FMT_LOCAL)
> > + return;
>
> I'm new to all this so this was a bit hard to follow. I'm confused with how
> commit 43518812d2 ("xfs: remove support for inlining data/extents into the
> inode fork") exacerbated the leak, isn't that commit about
> XFS_DINODE_FMT_EXTENTS?
Not specifically _EXTENTS, merely any fork (EXTENTS or LOCAL) whose
incore data was small enough to fit in if_inline_ata.
> Did we have cases where the format was XFS_DINODE_FMT_LOCAL and yet
> ifp->if_u1.if_data == ifp->if_u2.if_inline_data ?
An empty directory is 6 bytes, which is what you get with a fresh mkdir
or after deleting everything in the directory. Prior to the 43518812d2
patch we could get away with not even checking if we had to free if_data
when deleting a directory because it fit within if_inline_data.
--D
> Luis
> --
> 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
next prev parent reply other threads:[~2018-03-23 3:55 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-23 6:01 [PATCH] xfs: always free inline data before resetting inode fork during ifree Darrick J. Wong
2017-11-23 8:14 ` Christoph Hellwig
2018-03-23 1:30 ` Luis R. Rodriguez
2018-03-23 3:41 ` Darrick J. Wong [this message]
2018-03-23 17:08 ` Luis R. Rodriguez
2018-03-23 17:26 ` Darrick J. Wong
2018-03-23 18:23 ` Luis R. Rodriguez
2018-03-24 9:06 ` Greg Kroah-Hartman
2018-03-24 17:21 ` Darrick J. Wong
2018-03-26 4:54 ` Sasha Levin
2018-03-26 6:48 ` Darrick J. Wong
2018-03-26 17:39 ` Luis R. Rodriguez
2018-03-25 22:33 ` Dave Chinner
2018-03-26 23:54 ` Sasha Levin
2018-03-27 7:06 ` Michal Hocko
2018-03-27 19:54 ` Luis R. Rodriguez
2018-03-28 13:21 ` Michal Hocko
2018-03-28 19:33 ` Sasha Levin
2018-03-29 7:01 ` Michal Hocko
2018-03-28 1:11 ` Sasha Levin
2018-03-28 13:20 ` Michal Hocko
2018-03-28 3:32 ` Dave Chinner
2018-03-28 19:30 ` Sasha Levin
2018-03-28 19:40 ` Darrick J. Wong
2018-03-28 23:05 ` Dave Chinner
2018-03-29 18:12 ` Luis R. Rodriguez
2018-03-29 18:17 ` Josef Bacik
2018-03-29 18:36 ` Sasha Levin
2018-03-30 2:47 ` Sasha Levin
2018-03-30 19:49 ` Luis R. Rodriguez
2018-04-02 0:35 ` Sasha Levin
2018-03-31 22:02 ` Dave Chinner
2018-04-02 0:32 ` Sasha Levin
2018-04-03 1:46 ` Dave Chinner
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=20180323034145.GH4818@magnolia \
--to=darrick.wong@oracle.com \
--cc=linux-xfs@vger.kernel.org \
--cc=mcgrof@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).