From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: acc@CS.Stanford.EDU
Cc: linux-kernel@vger.kernel.org, mc@CS.Stanford.EDU
Subject: Re: [CHECKER] 15 potential pointer dereference errors in 2.4.3
Date: Thu, 05 Apr 2001 19:23:12 -0400 [thread overview]
Message-ID: <3ACCFE60.FF896272@mandrakesoft.com> (raw)
In-Reply-To: <20010405015251.A20904@Xenon.Stanford.EDU>
Andy Chou wrote:
> [BUG]
> /u2/acc/oses/linux/2.4.3/drivers/net/tokenring/tmsisa.c:274:tms_isa_probe: ERROR:NULL:273:274: Using
> unknown ptr "card" illegally! set by 'kmalloc':273
fixed
> [BUG]
> /u2/acc/oses/linux/2.4.3/drivers/pcmcia/rsrc_mgr.c:199:do_io_probe: ERROR:NULL:191:199: Using
> unknown ptr "b" illegally! set by 'kmalloc':191
fixed
--
Jeff Garzik | Sam: "Mind if I drive?"
Building 1024 | Max: "Not if you don't mind me clawing at the dash
MandrakeSoft | and shrieking like a cheerleader."
prev parent reply other threads:[~2001-04-05 23:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-05 8:52 [CHECKER] 15 potential pointer dereference errors in 2.4.3 Andy Chou
2001-04-05 9:40 ` Andy Chou
2001-04-05 20:56 ` Andy Chou
2001-04-05 23:23 ` Jeff Garzik [this message]
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=3ACCFE60.FF896272@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=acc@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