From: Nish Aravamudan <nish.aravamudan@gmail.com>
To: horst@schirmeier.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Badness in vsnprintf
Date: Thu, 26 Jan 2006 12:05:08 -0800 [thread overview]
Message-ID: <29495f1d0601261205u62aec435xfe6f94dc998934dc@mail.gmail.com> (raw)
In-Reply-To: <20060126195038.GB22994@quickstop.soohrt.org>
On 1/26/06, Horst Schirmeier <horst@schirmeier.com> wrote:
> Hi,
>
> since I'm testing the 2.6.16 release candidate, I'm encountering the
> following problem which manifests by a reported "Badness in vsnprintf"
> in dmesg. The system is still usable after this event.
I think this is also discussed here
http://lkml.org/lkml/2006/1/22/163. And there is a patch therein to
fix it (http://lkml.org/lkml/2006/1/24/237).
Thanks,
Nish
next prev parent reply other threads:[~2006-01-26 20:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-26 19:50 Badness in vsnprintf Horst Schirmeier
2006-01-26 20:05 ` Nish Aravamudan [this message]
2006-01-26 20:42 ` Horst Schirmeier
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=29495f1d0601261205u62aec435xfe6f94dc998934dc@mail.gmail.com \
--to=nish.aravamudan@gmail.com \
--cc=horst@schirmeier.com \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).