From: "David S. Miller" <davem@redhat.com>
To: jmorris@intercode.com.au
Cc: acc@CS.Stanford.EDU, linux-kernel@vger.kernel.org,
mc@CS.Stanford.EDU, kuznet@ms2.inr.ac.ru
Subject: Re: [PATCH] Re: [CHECKER] 112 potential memory leaks in 2.5.48
Date: Fri, 07 Feb 2003 01:24:11 -0800 (PST) [thread overview]
Message-ID: <20030207.012411.44088551.davem@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0302052259590.28037-100000@blackbird.intercode.com.au>
From: James Morris <jmorris@intercode.com.au>
Date: Wed, 5 Feb 2003 23:19:14 +1100 (EST)
Here's a fix for 2.5.59.
Applied, and backported to 2.4.x as the bug is there too.
next prev parent reply other threads:[~2003-02-07 9:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-05 1:13 [CHECKER] 112 potential memory leaks in 2.5.48 Andy Chou
2003-02-05 2:37 ` Rik van Riel
2003-02-05 2:42 ` [PATCH] " Rik van Riel
2003-02-05 16:19 ` James Bottomley
2003-02-05 6:06 ` Jochen Friedrich
2003-02-05 12:19 ` [PATCH] " James Morris
2003-02-07 9:24 ` David S. Miller [this message]
2003-02-05 12:20 ` James Morris
2003-02-07 9:25 ` David S. Miller
2003-02-05 18:16 ` Steve Lord
2003-02-05 23:48 ` Greg KH
2003-02-06 0:21 ` Andy Chou
2003-02-06 0:26 ` Greg KH
2003-02-06 2:26 ` Greg KH
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=20030207.012411.44088551.davem@redhat.com \
--to=davem@redhat.com \
--cc=acc@CS.Stanford.EDU \
--cc=jmorris@intercode.com.au \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=mc@CS.Stanford.EDU \
/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