Date: Thu, 26 Jan 2006 21:42:54 +0100
From: Horst Schirmeier <horst@schirmeier.com>
To: Nish Aravamudan <nish.aravamudan@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Badness in vsnprintf
Message-ID: <20060126204254.GC22994@quickstop.soohrt.org>
Mail-Followup-To: Nish Aravamudan <nish.aravamudan@gmail.com>,
	linux-kernel@vger.kernel.org
References: <20060126195038.GB22994@quickstop.soohrt.org> <29495f1d0601261205u62aec435xfe6f94dc998934dc@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <29495f1d0601261205u62aec435xfe6f94dc998934dc@mail.gmail.com>
User-Agent: Mutt/1.5.9i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 799
Lines: 22

On Thu, 26 Jan 2006, Nish Aravamudan wrote:
> On 1/26/06, Horst Schirmeier <horst@schirmeier.com> wrote:
> > 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, this resolves it temporarily.

Kind regards,
 Horst

-- 
PGP-Key 0xD40E0E7A
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/