Messages in this thread | | | From | Alexander Potapenko <> | Date | Mon, 10 Sep 2018 13:20:24 +0200 | Subject | Re: [PATCH] printk: inject caller information into the body of message |
| |
On Wed, Jun 20, 2018 at 3:06 PM Sergey Senozhatsky <sergey.senozhatsky@gmail.com> wrote: > > On (06/20/18 13:32), Dmitry Vyukov wrote: > > > So, if we could get rid of pr_cont() from the most important parts > > > (instruction dumps, etc) then I would just vote to leave pr_cont() > > > alone and avoid any handling of it in printk context tracking. Simply > > > because we wouldn't care about pr_cont(). This also could simplify > > > Tetsuo's patch significantly. > > > > Sounds good to me. > > Awesome. If you and Fengguang can combine forces and lead the > whole thing towards "we couldn't care of pr_cont() less", it > would be really huuuuuge. Go for it!
Sorry, folks, am I understanding right that pr_cont() and flushing the buffer on "\n" are two separate problems that can be handled outside Tetsuo's patchset, just assuming pr_cont() is unsupported? Or should the pr_cont() cleanup be a prerequisite for that?
> -ss > > -- > You received this message because you are subscribed to the Google Groups "syzkaller" group. > To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller+unsubscribe@googlegroups.com. > For more options, visit https://groups.google.com/d/optout.
-- Alexander Potapenko Software Engineer
Google Germany GmbH Erika-Mann-Straße, 33 80636 München
Geschäftsführer: Paul Manicle, Halimah DeLaine Prado Registergericht und -nummer: Hamburg, HRB 86891 Sitz der Gesellschaft: Hamburg
| |