From: David Sterba <dsterba@suse.cz>
To: linux-btrfs@vger.kernel.org
Cc: David Sterba <dsterba@suse.cz>
Subject: [PULL] [PATCH 0/5] Btrfs: leak in btrfs_find_item and cleanups
Date: Wed, 14 Jan 2015 19:36:30 +0100 [thread overview]
Message-ID: <cover.1421259762.git.dsterba@suse.cz> (raw)
Coverity for btrfs-progs spotted a variable leak in btrfs_find_item though the
same error is not reported in the kernel project and the code is the same. The
leak is very rare though and does not need to go to stable immediatelly. The
rest of patches are cleanups in the related codepaths.
You can also pull the changes from
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git fix/find-item-path-leak
Top commit: 1d4c08e0a60be3561
Base: 3.19-rc4
David Sterba (5):
btrfs: fix leak of path in btrfs_find_item
btrfs: cleanup, remove inode_item_info helper
btrfs: cleanup, remove inode_ref_info helper
btrfs: simplify insert_orphan_item
btrfs: expand btrfs_find_item if found_key is NULL
fs/btrfs/backref.c | 28 ++++++----------------------
fs/btrfs/backref.h | 3 ---
fs/btrfs/ctree.c | 18 +++++-------------
fs/btrfs/disk-io.c | 15 +++++++++++++--
fs/btrfs/inode.c | 10 +++++++---
fs/btrfs/scrub.c | 10 +++++++++-
fs/btrfs/tree-log.c | 11 ++++++-----
7 files changed, 46 insertions(+), 49 deletions(-)
--
1.8.4.5
next reply other threads:[~2015-01-14 18:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-14 18:36 David Sterba [this message]
2015-01-14 18:36 ` [PATCH 1/5] btrfs: fix leak of path in btrfs_find_item David Sterba
2015-01-14 18:36 ` [PATCH 2/5] btrfs: cleanup, remove inode_item_info helper David Sterba
2015-01-14 18:36 ` [PATCH 3/5] btrfs: cleanup, remove inode_ref_info helper David Sterba
2015-01-14 18:36 ` [PATCH 4/5] btrfs: simplify insert_orphan_item David Sterba
2015-01-14 18:36 ` [PATCH 5/5] btrfs: expand btrfs_find_item if found_key is NULL David Sterba
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=cover.1421259762.git.dsterba@suse.cz \
--to=dsterba@suse.cz \
--cc=linux-btrfs@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).