From: Pavel Machek <pavel@suse.cz>
To: pavel@ucw.cz
Cc: Ted Kremenek <kremenek@cs.stanford.edu>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
mc@cs.stanford.edu, Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [CHECKER] 12 potential leaks in kernel 2.5.69
Date: Mon, 26 May 2003 11:42:41 +0200 [thread overview]
Message-ID: <20030526094241.GD642@zaurus.ucw.cz> (raw)
In-Reply-To: <20030522100358.GB6708@wohnheim.fh-wedel.de>
Hi!
linux-2.5.69/drivers/message/i2o/i2o_core.c (lines 1668-1722)
> > [BUG/LEAK: may be false positive; status appears to be leaked elsewhere in
> > the function on purpose]
> >
> > m=i2o_wait_message(c, "AdapterReset");
> > if(m==0xFFFFFFFF)
> > return -ETIMEDOUT;
> > msg=(u32 *)(c->mem_offset+m);
> >
> > Start --->
> > status = pci_alloc_consistent(c->pdev, 4, &status_phys);
> >
> > ... DELETED 48 lines ...
> >
> > {
> > if((jiffies-time) >= 30*HZ)
> > {
> > printk(KERN_ERR "%s: Timeout waiting for IOP reset.\n",
> > c->name);
> > Error --->
> > return -ETIMEDOUT;
> > }
> > 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.
Perhaps comment should be added?
--
Pavel
Written on sharp zaurus, because my Velo1 broke. If you have Velo you don't need...
next prev parent reply other threads:[~2003-05-28 15:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-22 6:04 [CHECKER] 12 potential leaks in kernel 2.5.69 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
2003-05-26 9:42 ` Pavel Machek [this message]
-- strict thread matches above, loose matches on Subject: below --
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=20030526094241.GD642@zaurus.ucw.cz \
--to=pavel@suse.cz \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=kremenek@cs.stanford.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=mc@cs.stanford.edu \
--cc=pavel@ucw.cz \
/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