From: Oleg Drokin <green@namesys.com>
To: torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: [2.5] Memleak in fs/ufs/util.c
Date: Tue, 11 Mar 2003 19:19:08 +0300 [thread overview]
Message-ID: <20030311191908.A4381@namesys.com> (raw)
Hello!
There is trivial memleak on error exit path in
fs/ufs/util.c::_ubh_bread_()
See the patch attached.
Bye,
Oleg
===== fs/ufs/util.c 1.9 vs edited =====
--- 1.9/fs/ufs/util.c Thu May 23 17:19:01 2002
+++ edited/fs/ufs/util.c Tue Mar 11 19:17:01 2003
@@ -48,6 +48,7 @@
failed:
for (j = 0; j < i; j++)
brelse (ubh->bh[j]);
+ kfree(ubh);
return NULL;
}
reply other threads:[~2003-03-11 16:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030311191908.A4381@namesys.com \
--to=green@namesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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