From: Oleg Drokin <green@linuxhacker.ru>
To: alan@redhat.com, linux-kernel@vger.kernel.org
Cc: daniel.pirkl@email.cz
Subject: [2.4] ufs memleak
Date: Sun, 9 Mar 2003 20:34:33 +0300 [thread overview]
Message-ID: <20030309173433.GA27217@linuxhacker.ru> (raw)
Hello!
Seems there is ufs memleak in 2.4 code. See the patch attached.
Found with help of smatch + enchanced unfree script.
Bye,
Oleg
===== fs/ufs/util.c 1.5 vs edited =====
--- 1.5/fs/ufs/util.c Tue Feb 5 17:10:25 2002
+++ edited/fs/ufs/util.c Sun Mar 9 17:55:48 2003
@@ -47,6 +47,7 @@
failed:
for (j = 0; j < i; j++)
brelse (ubh->bh[j]);
+ kfree(ubh);
return NULL;
}
reply other threads:[~2003-03-09 17:24 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=20030309173433.GA27217@linuxhacker.ru \
--to=green@linuxhacker.ru \
--cc=alan@redhat.com \
--cc=daniel.pirkl@email.cz \
--cc=linux-kernel@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