From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Petr Mladek <pmladek@suse.com>
Cc: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
syzbot <syzbot+43e93968b964e369db0b@syzkaller.appspotmail.com>,
linux-kernel@vger.kernel.org, rostedt@goodmis.org,
syzkaller-bugs@googlegroups.com,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.com>,
linux-serial@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: possible deadlock in console_unlock
Date: Tue, 19 Jun 2018 17:08:12 +0900 [thread overview]
Message-ID: <20180619080812.GC405@jagdpanzerIV> (raw)
In-Reply-To: <20180619080412.zkdanx6bmq5qm3dz@pathway.suse.cz>
On (06/19/18 10:04), Petr Mladek wrote:
> > >
> > > We could allow nesting. It is just a matter of how many bits we
> > > reserve for it in printk_context variable.
> > [..]
> > > In each case, I would like to keep the printk_safe context usage
> > > at minimum. It has its own problems caused by limited per-cpu buffers
> > > and the need to flush them.
> >
> > May be. Every new printk_safe flavour comes with increasing memory
> > usage.
>
> This must be a misunderstanding. My intention was to introduce
> printk_deferred() context. Where any printk() called in this
> context would behave like printk_deferred(). It does not need
> any extra buffers.
Ah, got it. Yes, this can work.
-ss
next prev parent reply other threads:[~2018-06-19 8:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <00000000000087008b056df8fbb3@google.com>
2018-06-07 5:10 ` possible deadlock in console_unlock Sergey Senozhatsky
2018-06-07 11:00 ` Petr Mladek
2018-06-07 11:40 ` Tetsuo Handa
2018-06-07 14:03 ` Sergey Senozhatsky
2018-06-07 14:01 ` Sergey Senozhatsky
2018-06-08 8:18 ` Petr Mladek
2018-06-15 8:38 ` Sergey Senozhatsky
2018-06-19 8:04 ` Petr Mladek
2018-06-19 8:08 ` Sergey Senozhatsky [this message]
2019-02-20 10:52 ` Tetsuo Handa
2019-11-25 2:41 ` syzbot
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=20180619080812.GC405@jagdpanzerIV \
--to=sergey.senozhatsky.work@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky@gmail.com \
--cc=syzbot+43e93968b964e369db0b@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
/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).