linux-serial.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* BUG: sleeping function called from invalid context in console_lock
       [not found] <42c2c0c4-9ee2-6426-8c3c-2585e0345fcb@huawei.com>
@ 2023-09-18 13:35 ` yiyang (D)
  2023-09-18 15:19   ` Greg Kroah-Hartman
  0 siblings, 1 reply; 6+ messages in thread
From: yiyang (D) @ 2023-09-18 13:35 UTC (permalink / raw)
  To: Greg Kroah-Hartman, Jiri Slaby, hedonistsmith, daniel.starke; +Cc: linux-serial

In recent years, this problem has been reported in syzkaller all the time.

Link: https://syzkaller.appspot.com/bug?extid=dbac96d8e73b61aa559c

Historically, the developers have tried to fix this problem by use mutex 
instead spinlock, but it didn't solve the problem..

Link: https://lore.kernel.org/all/20220826193545.20363-1-pchelkin@ispras.ru/

Other developers have recently reported this problem, but no one has 
continued to try to fix it.

Link: 
https://lore.kernel.org/all/20230420082153.6711-1-daniel.starke@siemens.com/

Anyway, do we have any ideas for solving this problem?

-- 
yiyang
.

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: BUG: sleeping function called from invalid context in console_lock
  2023-09-18 13:35 ` BUG: sleeping function called from invalid context in console_lock yiyang (D)
@ 2023-09-18 15:19   ` Greg Kroah-Hartman
  2023-09-27  7:48     ` yiyang (D)
  2023-09-27  9:15     ` yiyang (D)
  0 siblings, 2 replies; 6+ messages in thread
From: Greg Kroah-Hartman @ 2023-09-18 15:19 UTC (permalink / raw)
  To: yiyang (D); +Cc: Jiri Slaby, hedonistsmith, daniel.starke, linux-serial

On Mon, Sep 18, 2023 at 09:35:23PM +0800, yiyang (D) wrote:
> In recent years, this problem has been reported in syzkaller all the time.
> 
> Link: https://syzkaller.appspot.com/bug?extid=dbac96d8e73b61aa559c
> 
> Historically, the developers have tried to fix this problem by use mutex
> instead spinlock, but it didn't solve the problem..
> 
> Link: https://lore.kernel.org/all/20220826193545.20363-1-pchelkin@ispras.ru/
> 
> Other developers have recently reported this problem, but no one has
> continued to try to fix it.
> 
> Link:
> https://lore.kernel.org/all/20230420082153.6711-1-daniel.starke@siemens.com/
> 
> Anyway, do we have any ideas for solving this problem?

Nope!  Why do you think this is something that even needs to be
addressed?

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: BUG: sleeping function called from invalid context in console_lock
  2023-09-18 15:19   ` Greg Kroah-Hartman
@ 2023-09-27  7:48     ` yiyang (D)
  2023-09-27  8:24       ` Greg Kroah-Hartman
  2023-09-27  9:15     ` yiyang (D)
  1 sibling, 1 reply; 6+ messages in thread
From: yiyang (D) @ 2023-09-27  7:48 UTC (permalink / raw)
  To: Greg Kroah-Hartman; +Cc: Jiri Slaby, hedonistsmith, daniel.starke, linux-serial

On 2023/9/18 23:19, Greg Kroah-Hartman wrote:
> On Mon, Sep 18, 2023 at 09:35:23PM +0800, yiyang (D) wrote:
>> In recent years, this problem has been reported in syzkaller all the time.
>>
>> Link: https://syzkaller.appspot.com/bug?extid=dbac96d8e73b61aa559c
>>
>> Historically, the developers have tried to fix this problem by use mutex
>> instead spinlock, but it didn't solve the problem..
>>
>> Link: https://lore.kernel.org/all/20220826193545.20363-1-pchelkin@ispras.ru/
>>
>> Other developers have recently reported this problem, but no one has
>> continued to try to fix it.
>>
>> Link:
>> https://lore.kernel.org/all/20230420082153.6711-1-daniel.starke@siemens.com/
>>
>> Anyway, do we have any ideas for solving this problem?
> 
> Nope!  Why do you think this is something that even needs to be
> addressed?
> .
> 
Kernel only perform cannot sleep operations in atomic context, as 
otherwise a system hang or crash may occur.

So there's a risk to this problem.


^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: BUG: sleeping function called from invalid context in console_lock
  2023-09-27  7:48     ` yiyang (D)
@ 2023-09-27  8:24       ` Greg Kroah-Hartman
  0 siblings, 0 replies; 6+ messages in thread
From: Greg Kroah-Hartman @ 2023-09-27  8:24 UTC (permalink / raw)
  To: yiyang (D); +Cc: Jiri Slaby, hedonistsmith, daniel.starke, linux-serial

On Wed, Sep 27, 2023 at 03:48:33PM +0800, yiyang (D) wrote:
> On 2023/9/18 23:19, Greg Kroah-Hartman wrote:
> > On Mon, Sep 18, 2023 at 09:35:23PM +0800, yiyang (D) wrote:
> > > In recent years, this problem has been reported in syzkaller all the time.
> > > 
> > > Link: https://syzkaller.appspot.com/bug?extid=dbac96d8e73b61aa559c
> > > 
> > > Historically, the developers have tried to fix this problem by use mutex
> > > instead spinlock, but it didn't solve the problem..
> > > 
> > > Link: https://lore.kernel.org/all/20220826193545.20363-1-pchelkin@ispras.ru/
> > > 
> > > Other developers have recently reported this problem, but no one has
> > > continued to try to fix it.
> > > 
> > > Link:
> > > https://lore.kernel.org/all/20230420082153.6711-1-daniel.starke@siemens.com/
> > > 
> > > Anyway, do we have any ideas for solving this problem?
> > 
> > Nope!  Why do you think this is something that even needs to be
> > addressed?
> > .
> > 
> Kernel only perform cannot sleep operations in atomic context, as otherwise
> a system hang or crash may occur.
> 
> So there's a risk to this problem.
> 

Have you see this risk in real workloads?  If so, great, please provide
a working solution that is tested and verified to work properly.

good luck!

greg k-h

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: BUG: sleeping function called from invalid context in console_lock
  2023-09-18 15:19   ` Greg Kroah-Hartman
  2023-09-27  7:48     ` yiyang (D)
@ 2023-09-27  9:15     ` yiyang (D)
  2023-09-27  9:41       ` Greg Kroah-Hartman
  1 sibling, 1 reply; 6+ messages in thread
From: yiyang (D) @ 2023-09-27  9:15 UTC (permalink / raw)
  To: Greg Kroah-Hartman; +Cc: Jiri Slaby, hedonistsmith, daniel.starke, linux-serial

On 2023/9/18 23:19, Greg Kroah-Hartman wrote:
> On Mon, Sep 18, 2023 at 09:35:23PM +0800, yiyang (D) wrote:
>> In recent years, this problem has been reported in syzkaller all the time.
>>
>> Link: https://syzkaller.appspot.com/bug?extid=dbac96d8e73b61aa559c
>>
>> Historically, the developers have tried to fix this problem by use mutex
>> instead spinlock, but it didn't solve the problem..
>>
>> Link: https://lore.kernel.org/all/20220826193545.20363-1-pchelkin@ispras.ru/
>>
>> Other developers have recently reported this problem, but no one has
>> continued to try to fix it.
>>
>> Link:
>> https://lore.kernel.org/all/20230420082153.6711-1-daniel.starke@siemens.com/
>>
>> Anyway, do we have any ideas for solving this problem?
> 
> Nope!  Why do you think this is something that even needs to be
> addressed?
> .
> 
This problem seems to be a CVE problem.
https://nvd.nist.gov/vuln/detail/CVE-2023-31082



^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: BUG: sleeping function called from invalid context in console_lock
  2023-09-27  9:15     ` yiyang (D)
@ 2023-09-27  9:41       ` Greg Kroah-Hartman
  0 siblings, 0 replies; 6+ messages in thread
From: Greg Kroah-Hartman @ 2023-09-27  9:41 UTC (permalink / raw)
  To: yiyang (D); +Cc: Jiri Slaby, hedonistsmith, daniel.starke, linux-serial

On Wed, Sep 27, 2023 at 05:15:25PM +0800, yiyang (D) wrote:
> On 2023/9/18 23:19, Greg Kroah-Hartman wrote:
> > On Mon, Sep 18, 2023 at 09:35:23PM +0800, yiyang (D) wrote:
> > > In recent years, this problem has been reported in syzkaller all the time.
> > > 
> > > Link: https://syzkaller.appspot.com/bug?extid=dbac96d8e73b61aa559c
> > > 
> > > Historically, the developers have tried to fix this problem by use mutex
> > > instead spinlock, but it didn't solve the problem..
> > > 
> > > Link: https://lore.kernel.org/all/20220826193545.20363-1-pchelkin@ispras.ru/
> > > 
> > > Other developers have recently reported this problem, but no one has
> > > continued to try to fix it.
> > > 
> > > Link:
> > > https://lore.kernel.org/all/20230420082153.6711-1-daniel.starke@siemens.com/
> > > 
> > > Anyway, do we have any ideas for solving this problem?
> > 
> > Nope!  Why do you think this is something that even needs to be
> > addressed?
> > .
> > 
> This problem seems to be a CVE problem.
> https://nvd.nist.gov/vuln/detail/CVE-2023-31082

If you think CVEs are actually valid for the kernel (hint, they aren't),
then wonderful, please work to resolve this issue.

Again, good luck!

greg k-h

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2023-09-27  9:41 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [not found] <42c2c0c4-9ee2-6426-8c3c-2585e0345fcb@huawei.com>
2023-09-18 13:35 ` BUG: sleeping function called from invalid context in console_lock yiyang (D)
2023-09-18 15:19   ` Greg Kroah-Hartman
2023-09-27  7:48     ` yiyang (D)
2023-09-27  8:24       ` Greg Kroah-Hartman
2023-09-27  9:15     ` yiyang (D)
2023-09-27  9:41       ` Greg Kroah-Hartman

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).