From: Andrew Morton <andrewm@uow.edu.au>
To: Troels Walsted Hansen <troels@thule.no>
Cc: linux-kernel@vger.kernel.org, greg@wind.enjellic.com,
joey@linux.de, David Hinds <dhinds@sonic.net>
Subject: Re: [PATCH] klogd busy loop on zero byte (output from 3c59x driver)
Date: Thu, 11 Jan 2001 23:03:31 +1100 [thread overview]
Message-ID: <3A5DA113.DC8DB21C@uow.edu.au> (raw)
In-Reply-To: <CKECLHEEHJOPHGPCOCKPEECCCCAA.troels@thule.no>
Troels Walsted Hansen wrote:
>
> Hi all.
>
> I found a bug in the sysklogd package version 1.4. When it encounters a zero
> byte in the kernel logging output, the text parser enters a busy loop. I
> came upon it when the 3c59x driver from kernel 2.4.0 started outputting two
> zero bytes for the product code of my laptop's 3Com card. It could be argued
> that the kernel should never output zero bytes in the logging info, but
> obviously that will happen from time to time.
Yep. %02x%02x it now is.
The code in question was snitched from pcmcia-cs's 3c575_cb.c, and
I assume David would have heard if it was busting klogd. Maybe
there's a klogd version problem, or maybe your NIC's EEPROM is hosed?
-
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-11 11:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-11 8:48 [PATCH] klogd busy loop on zero byte (output from 3c59x driver) Troels Walsted Hansen
2001-01-11 11:41 ` Manfred
2001-01-11 12:03 ` Andrew Morton [this message]
2001-01-11 14:06 ` Troels Walsted Hansen
2001-01-11 17:30 ` David Hinds
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=3A5DA113.DC8DB21C@uow.edu.au \
--to=andrewm@uow.edu.au \
--cc=dhinds@sonic.net \
--cc=greg@wind.enjellic.com \
--cc=joey@linux.de \
--cc=linux-kernel@vger.kernel.org \
--cc=troels@thule.no \
/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