From: David Sterba <dsterba@suse.cz>
To: linux-btrfs@vger.kernel.org
Cc: David Sterba <dsterba@suse.cz>
Subject: [PATCH 0/5] Btrfs progs, coverity fixes for 3.18-rc3
Date: Tue, 30 Dec 2014 15:57:34 +0100 [thread overview]
Message-ID: <cover.1419951036.git.dsterba@suse.cz> (raw)
Several issues reported by coverity, minor resource leaks and two bugfixes.
David Sterba (5):
btrfs-progs: check, fix path leak in error branch
btrfs-progs: fi show, don't leak canonical path
btrfs-progs: check, missing parens around compound block in
find_normal_file_extent
btrfs-progs: fix overflow check in btrfs_insert_inode_ref
btrfs-progs: fix minor leak of dev_info in btrfs_scan_kernel
cmds-check.c | 8 +++++---
cmds-filesystem.c | 6 ++++--
inode-item.c | 2 +-
3 files changed, 10 insertions(+), 6 deletions(-)
--
2.1.3
next reply other threads:[~2014-12-30 14:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-30 14:57 David Sterba [this message]
2014-12-30 14:57 ` [PATCH 1/5] btrfs-progs: check, fix path leak in error branch David Sterba
2014-12-30 14:57 ` [PATCH 2/5] btrfs-progs: fi show, don't leak canonical path David Sterba
2014-12-30 14:57 ` [PATCH 3/5] btrfs-progs: check, missing parens around compound block in find_normal_file_extent David Sterba
2014-12-30 14:57 ` [PATCH 4/5] btrfs-progs: fix overflow check in btrfs_insert_inode_ref David Sterba
2014-12-30 14:57 ` [PATCH 5/5] btrfs-progs: fix minor leak of dev_info in btrfs_scan_kernel 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.1419951036.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.