From: Joern Engel <joern@wohnheim.fh-wedel.de>
To: Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>
Cc: Oleg Drokin <green@linuxhacker.ru>,
"Randy.Dunlap" <rddunlap@osdl.org>,
alan@lxorguk.ukuu.org.uk, linux-kernel@vger.kernel.org,
deanna_bonds@adaptec.com
Subject: Re: dpt_i2o.c fix for possibly memory corruption on reset timeout
Date: Fri, 14 Mar 2003 13:02:25 +0100 [thread overview]
Message-ID: <20030314120224.GA30034@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <200303140921.h2E9Lqu08107@Port.imtp.ilyichevsk.odessa.ua>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=unknown-8bit, Size: 614 bytes --]
On Fri, 14 March 2003 11:18:49 +0200, Denis Vlasenko wrote:
>
> I don't like the whole idea that mem leak is tolerable.
>
> Can we just add a 4 byte scratch pad status to
> struct _adpt_hba? Let it scribble there...
I've had the same idea, but there might be some pitfalls around.
The problem boils down to the users of the buffer. Is it per-device,
per-process, per-whatever?
Once this is known I'm all for putting the buffer into a per-whatever
data structure. But someone has to understand the driver first. :)
Jörn
--
Everything should be made as simple as possible, but not simpler.
-- Albert Einstein
next prev parent reply other threads:[~2003-03-14 11:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-13 18:28 dpt_i2o.c memleak/incorrectness Oleg Drokin
2003-03-13 19:44 ` Alan Cox
2003-03-13 18:41 ` dpt_i2o.c fix for possibly memory corruption on reset timeout Oleg Drokin
2003-03-13 18:51 ` Randy.Dunlap
2003-03-13 18:56 ` Oleg Drokin
2003-03-14 9:18 ` Denis Vlasenko
2003-03-14 12:02 ` Joern Engel [this message]
2003-03-14 14:19 ` Alan Cox
2003-03-14 13:39 ` Joern Engel
2003-03-14 13:43 ` Oleg Drokin
2003-03-14 15:26 ` Alan Cox
2003-03-13 18:58 ` dpt_i2o.c memleak/incorrectness Bryan Andersen
2003-03-15 16:15 ` Horst von Brand
2003-03-13 19:38 ` Now i2o_core.c memleak/incorrectness? Oleg Drokin
2003-03-14 0:42 ` Alan Cox
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=20030314120224.GA30034@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=deanna_bonds@adaptec.com \
--cc=green@linuxhacker.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.org \
--cc=vda@port.imtp.ilyichevsk.odessa.ua \
/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®