From: Tejun Heo <htejun@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: torvalds@linux-foundation.org, randy.dunlap@oracle.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] printk: implement printk_buf overflow warning
Date: Thu, 14 Feb 2008 09:14:10 +0900 [thread overview]
Message-ID: <47B387D2.5050808@gmail.com> (raw)
In-Reply-To: <20080213155954.c1d0b6ee.akpm@linux-foundation.org>
Andrew Morton wrote:
> On Wed, 13 Feb 2008 18:03:12 +0900
> Tejun Heo <htejun@gmail.com> wrote:
>
>> printk silently truncates messages longer than 1024 - 1 bytes.
>> Implement overflow detection and append "$PRINTK_BUF_OVERFLOW$\n" to
>> truncated messages.
>
> I don't think I've ever heard of anyone managing to overflow the printk
> buffer and it's hard to imagine how a sane person could manage to do this.
>
> I assume this is happening because of changes in your other patchset, and
> that this change is hence associated with those changes and should probably
> be a part of the same patch series?
I thought this went well with the recursion warning. I'll move it into
the mprintk patchset.
Thanks.
--
tejun
prev parent reply other threads:[~2008-02-14 0:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-13 9:03 [PATCH] printk: implement printk_buf overflow warning Tejun Heo
2008-02-13 23:59 ` Andrew Morton
2008-02-14 0:14 ` Tejun Heo [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=47B387D2.5050808@gmail.com \
--to=htejun@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=torvalds@linux-foundation.org \
/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