Messages in this thread | | | From | Dmitry Torokhov <> | Subject | Re: Fw: Re: oops in choose_configuration() | Date | Tue, 7 Mar 2006 23:44:59 -0500 |
| |
On Tuesday 07 March 2006 23:28, Joe Korty wrote: > On Tue, Mar 07, 2006 at 04:57:39PM -0800, Linus Torvalds wrote: > > > Well, snprintf() should be safe, though. It will warn if the caller is > > lazy, but these days, the thing does > > > > max(buf_size - len, 0) > > > > which should mean that the input layer passes in 0 instead of a negative > > number. And snprintf() will then _not_ print anything. > > I assume this is a typo, and you meant scnprintf? AFAIK, snprintf has > the same ol' bad behavior when #bytes-to-be-written > #bytes-in-buffer. >
No, we do want to know if output was truncated or not so snprintf is used.
-- Dmitry - 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/
| |