From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
Cc: Ted Kremenek <kremenek@cs.stanford.edu>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
mc@cs.stanford.edu
Subject: Re: [CHECKER] 12 potential leaks in kernel 2.5.69
Date: 22 May 2003 10:50:10 +0100 [thread overview]
Message-ID: <1053597009.2534.0.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <20030522100358.GB6708@wohnheim.fh-wedel.de>
> > schedule();
> > barrier();
>
> Iirc, the above will leak 4 bytes (plus overhead) once per kernel
> boot and controller. This only happens for broken hardware and the
> alternative is memory corruption, depending on how broken the hardware
> is. Wontfix.
>
> Alan, was that correct?
It should only leak in the error path case. If the controller didnt reply
then it still owns that ram and for the sake of a few bytes its better to
play safe yes
next prev parent reply other threads:[~2003-05-22 10:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-22 6:04 Ted Kremenek
2003-05-22 7:46 ` David S. Miller
2003-05-22 10:03 ` Jörn Engel
2003-05-22 9:50 ` Alan Cox [this message]
2003-05-26 9:42 ` Pavel Machek
2003-05-22 17:34 Jean Tourrilhes
2003-05-23 8:11 ` Ted Kremenek
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=1053597009.2534.0.camel@dhcp22.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=joern@wohnheim.fh-wedel.de \
--cc=kremenek@cs.stanford.edu \
--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
all inboxes | Powered by JetHome®