public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nathan Myers <ncm-nospam@cantrip.org>
To: linux-kernel@vger.kernel.org
Cc: marcelo@conectiva.com.br, torvalds@transmeta.com,
	alan@redhat.com, VDA@port.imtp.ilyichevsk.odessa.ua
Subject: [PATCH] memory corruption in i2o
Date: Tue, 11 Dec 2001 02:10:32 +0000	[thread overview]
Message-ID: <20011211021032.A65086@cantrip.org> (raw)

Some weeks back "VDA@port.imtp.ilyichevsk.odessa.ua" reported in

  http://marc.theaimsgroup.com/?l=linux-kernel&m=100633930427682&w=2

a bug in an i2o header file that causes kernel memory corruption.  
The obvious fix was posted several times; this one from Andreas Dilger

  http://marc.theaimsgroup.com/?l=linux-kernel&m=100688659819007&w=2

is typical.  The fix appears not to have been picked up in 2.4.17-pre8.
There is no i2o maintainer listed in MAINTAINERS.

With a 2.4.17 release candidate coming up, it's probably time to 
apply it.

The original posting noted several other similar bugs, for which it
and subsequent postings suggested fixes, e.g.

  http://marc.theaimsgroup.com/?l=linux-kernel&m=100634117104111&w=2

Is anybody going to pick up _any_ of these fixes, or do they just rot
until enough kernel crashes get reported with enough detail to implicate
the identified bugs?  

Nathan Myers
ncm at cantrip dot org

             reply	other threads:[~2001-12-11  2:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-11  2:10 Nathan Myers [this message]
2001-12-11 12:59 ` [PATCH] memory corruption in i2o 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=20011211021032.A65086@cantrip.org \
    --to=ncm-nospam@cantrip.org \
    --cc=VDA@port.imtp.ilyichevsk.odessa.ua \
    --cc=alan@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    --cc=torvalds@transmeta.com \
    /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