From: tinguely@sgi.com
To: xfs@oss.sgi.com
Subject: [PATCH 0/2] xfsprogs misc memory leaks
Date: Sat, 05 Oct 2013 21:51:51 -0500 [thread overview]
Message-ID: <20131006025151.573856006@sgi.com> (raw)
Here are the xfsprog versions of the Coverity 134683 and 134681 found
leak patches. They are the same as the kernel except the file names.
--Mark.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2013-10-06 2:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-06 2:51 tinguely [this message]
2013-10-06 2:51 ` [PATCH 1/2] xfsprogs: fix leak in xfs_log_recover_add_to_trans tinguely
2013-10-06 2:51 ` [PATCH 2/2] xfs: fix memory leak in xfs_dir2_node_removename tinguely
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=20131006025151.573856006@sgi.com \
--to=tinguely@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