mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@uni-koblenz.de>
To: "Ryan W. Maple" <ryan@guardiandigital.com>
Cc: Justin Guyett <justin@soze.net>, james bond <difda@hotmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: BIG PROBLEM
Date: Thu, 28 Jun 2001 23:46:59 +0200	[thread overview]
Message-ID: <20010628234659.A8105@bacchus.dhis.org> (raw)
In-Reply-To: <Pine.LNX.4.33.0106281413080.23200-100000@gw.soze.net> <Pine.LNX.4.10.10106281734140.11669-100000@mastermind.inside.guardiandigital.com>
In-Reply-To: <Pine.LNX.4.10.10106281734140.11669-100000@mastermind.inside.guardiandigital.com>; from ryan@guardiandigital.com on Thu, Jun 28, 2001 at 05:35:14PM -0400

On Thu, Jun 28, 2001 at 05:35:14PM -0400, Ryan W. Maple wrote:

> Check out:  http://bugs.debian.org/85478
> 
>   "When klogd's LogLine() function encounters a null byte in state
>    PARSING_TEXT, it will loop infinitely.  More precisely, copyin()
>    will treat the null byte as a delimiter - unlike LogLine(), which
>    will invoke copyin() ever and ever again."
> 
> Kinda off-topic, but I just wanted to prove that the bug was in klogd and
> not the kernel. :)

The kernel definately shouldn't communicate with the user using NUL chars.

  Ralf

      reply	other threads:[~2001-06-28 21:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-28 18:49 james bond
2001-06-28 19:07 ` Alan Cox
2001-06-28 19:33   ` Ryan W. Maple
2001-06-28 20:59 ` Ralf Baechle
2001-06-28 21:17   ` Justin Guyett
2001-06-28 21:35     ` Ryan W. Maple
2001-06-28 21:46       ` Ralf Baechle [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=20010628234659.A8105@bacchus.dhis.org \
    --to=ralf@uni-koblenz.de \
    --cc=difda@hotmail.com \
    --cc=justin@soze.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ryan@guardiandigital.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

all inboxes | Powered by JetHome®