From: Oleg Drokin <green@linuxhacker.ru>
To: Joern Engel <joern@wohnheim.fh-wedel.de>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
vda@port.imtp.ilyichevsk.odessa.ua,
"Randy.Dunlap" <rddunlap@osdl.org>,
Linux Kernel Mailing List <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 16:43:28 +0300 [thread overview]
Message-ID: <20030314134328.GA8804@linuxhacker.ru> (raw)
In-Reply-To: <20030314133942.GA23062@wohnheim.fh-wedel.de>
Hello!
On Fri, Mar 14, 2003 at 02:39:42PM +0100, Joern Engel wrote:
> > > Can we just add a 4 byte scratch pad status to
> > > struct _adpt_hba? Let it scribble there...
> > Its 4 bytes (+ slab overhead), its far safer if this happens to say
> > its gone forever. Its owned by the I2O controller now and it never
> > gave it back
> How about an (optional) counter then? If you can show that this case
> is hit zero times during operation, noone will complain. On the other
> hand, if some hardware hits this problem 1000+ times, we have a good
> reason to find another solution.
> I'd volunteer to create the patch, if the idea is accepted.
Well, if some hardware would do so, then users would go here and complain
about kernel being noisy on certain hardware. (message is printed each
time this happens). Have not happened so far.
Bye,
Oleg
next prev parent reply other threads:[~2003-03-14 13:36 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
2003-03-14 14:19 ` Alan Cox
2003-03-14 13:39 ` Joern Engel
2003-03-14 13:43 ` Oleg Drokin [this message]
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=20030314134328.GA8804@linuxhacker.ru \
--to=green@linuxhacker.ru \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=deanna_bonds@adaptec.com \
--cc=joern@wohnheim.fh-wedel.de \
--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