From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Yao HongBo <yaohongbo@huawei.com>
Cc: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
linuxarm@huawei.com, linux-kernel@vger.kernel.org
Subject: Re: possible deadlock in console_unlock
Date: Mon, 18 Feb 2019 14:46:49 +0900 [thread overview]
Message-ID: <20190218054649.GA26686@jagdpanzerIV> (raw)
In-Reply-To: <71b097a7-03c5-8a65-76fa-24312b452b51@huawei.com>
Hi,
On (02/16/19 15:59), Yao HongBo wrote:
> > GFP_NOWARN is probably the best option for now. Yes, it, maybe,
> > will not work for fault-injection cases; but printk_safe approach
> > is harder to push for, especially given that printk_safe maybe will
> > not even exist in the future.
>
> I have tried GFP_NOWARN, but the problem still exists.
> Only print_safe contexts for tty locks can solve the problem.
> My test scenario is falt-injection.
Oh, I see. Yes, fault-injection is special.
I suspect that this patch series can be helpful then
https://lore.kernel.org/lkml/20181016050428.17966-1-sergey.senozhatsky@gmail.com/T/#u
but first we need to figure out if printk_safe will
stay in the kernel (this will take some time).
-ss
next prev parent reply other threads:[~2019-02-18 5:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-16 6:36 possible deadlock in console_unlock Yao HongBo
2019-02-16 7:21 ` Sergey Senozhatsky
2019-02-16 7:46 ` Sergey Senozhatsky
2019-02-16 7:59 ` Yao HongBo
2019-02-18 5:46 ` Sergey Senozhatsky [this message]
2019-02-18 12:09 ` Yao HongBo
2019-02-18 14:07 ` Yao HongBo
2019-02-19 1:32 ` Sergey Senozhatsky
2019-02-19 2:48 ` Yao HongBo
-- strict thread matches above, loose matches on Subject: below --
2018-06-06 13:17 syzbot
2018-06-07 4:44 ` syzbot
2018-06-07 5:10 ` 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
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=20190218054649.GA26686@jagdpanzerIV \
--to=sergey.senozhatsky.work@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=sergey.senozhatsky@gmail.com \
--cc=yaohongbo@huawei.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