On Wed, Sep 26, 2012 at 07:58:45PM +0200, Jan H. Schönherr wrote: > From: Jan H. Schönherr <schn...@cs.tu-berlin.de> > > The meaning of LOG_CONT is unclear, i. e., whether a message is a starting, > ending, or middle fragment. Unfortunately, this cannot be inferred from > the LOG_PREFIX and LOG_NEWLINE flags, as they are not always kept. > Furthermore, in some cases LOG_CONT is set, although it is unknown if > there will be a continuation. This leads to wrongly concatenated output. > > Fix this by dropping LOG_CONT and rely on LOG_PREFIX and LOG_NEWLINE to > distinguish the type of fragment. That is, if LOG_PREFIX is set, this > fragment does not continue the previous fragment. And if LOG_NEWLINE is > set, this fragment is not continued by the next fragment. > > (Unfortunately, we still have to look at the previous fragment to catch the > case of an unset LOG_PREFIX on this fragment, but a set LOG_NEWLINE on > the previous fragment.) > > Signed-off-by: Jan H. Schönherr <schn...@cs.tu-berlin.de> > --- > Against v3.6-rc7, only lightly tested.
Well, against linux-next and highly tested would be best. It's a bit late to get this into linux-next for 3.7, how important is it really? thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
