[Kgdb-bugreport] 答复: [PATCH V10] kdb: Fix the deadlock issue in KDB debugging.

>> Signed-off-by: Greg KH > >I have NOT signed off on this commit. You just said that I made a legal >statement about this commit without that actually being true??? > >Sorry, but that is flat out not acceptable at all. Please go work with your >company lawyers to figure out what you did and

[Kgdb-bugreport] 答复: 答复: 答复: [PATCH V10] kdb: Fix the deadlock issue in KDB debugging.

>On Wed, Apr 10, 2024 at 06:10:10AM +0000, Liuye wrote: >> >On Wed, Apr 10, 2024 at 05:54:08AM +, Liuye wrote: >> >> >> Signed-off-by: Greg KH >> >> > >> >> >I have NOT signed off on this commit. You just said that I made a leg

[Kgdb-bugreport] 答复: 答复: [PATCH V10] kdb: Fix the deadlock issue in KDB debugging.

>On Wed, Apr 10, 2024 at 05:54:08AM +0000, Liuye wrote: >> >> Signed-off-by: Greg KH >> > >> >I have NOT signed off on this commit. You just said that I made a legal >> >statement about this commit without that actually being true??? >> > &g

[Kgdb-bugreport] 答复: 答复: 答复: 答复: [PATCH V10] kdb: Fix the deadlock issue in KDB debugging.

>On Wed, Apr 10, 2024 at 06:30:59AM +0000, Liuye wrote: >> >On Wed, Apr 10, 2024 at 06:10:10AM +, Liuye wrote: >> >> >On Wed, Apr 10, 2024 at 05:54:08AM +, Liuye wrote: >> >> >> >> Signed-off-by: Greg KH >> >> >> > &g

[Kgdb-bugreport] Re：[PATCH V11] kdb: Fix the deadlock issue in KDB debugging.

>From: LiuYe > >Currently, if CONFIG_KDB_KEYBOARD is enabled, then kgdboc will >attempt to use schedule_work() to provoke a keyboard reset when >transitioning out of the debugger and back to normal operation. >This can cause deadlock because schedule_work() is not NMI-safe.

Re: [Kgdb-bugreport] Re：[PATCH V11] kdb: Fix the deadlock issue in KDB debugging.

>On Wed, Apr 17, 2024 at 11:01:56AM +0000, Liuye wrote: >> >--- >> >V10 -> V11: Revert to V9 >> >V9 -> V10 : Add Signed-off-by of Greg KH and Andy Shevchenko, Acked >> >by of Daniel Thompson >> >V8 -> V9: Modify call trace format

[Kgdb-bugreport] 答复: 答复: [PATCH] kdb: Fix the deadlock issue in KDB debugging.

I know that you said schedule_work is not NMI save, which is the first issue. Perhaps it can be fixed using irq_work_queue. But even if irq_work_queue is used to implement it, there will still be a deadlock problem because slave cpu1 still has not released the running queue lock of master CPU0.

[Kgdb-bugreport] 答复: 答复: 答复: [PATCH] kdb: Fix the deadlock issue in KDB debugging.

>On Tue, Mar 12, 2024 at 08:37:11AM +0000, Liuye wrote: >> I know that you said schedule_work is not NMI save, which is the first >> issue. Perhaps it can be fixed using irq_work_queue. But even if >> irq_work_queue is used to implement it, there will still be a deadloc

[Kgdb-bugreport] 答复: 答复: 答复: 答复: 答复: 答复: [PATCH] kdb: Fix the deadlock issue in KDB debugging.

>On Thu, Mar 14, 2024 at 07:06:22AM +0000, Liuye wrote: >> >On Wed, Mar 13, 2024 at 01:22:17AM +, Liuye wrote: >> >> >On Tue, Mar 12, 2024 at 10:04:54AM +, Liuye wrote: >> >> >> >On Tue, Mar 12, 2024 at 08:37:11AM +, Liuye wrote

[Kgdb-bugreport] 答复: 答复: 答复: 答复: [PATCH] kdb: Fix the deadlock issue in KDB debugging.

>On Tue, Mar 12, 2024 at 10:04:54AM +0000, Liuye wrote: >> >On Tue, Mar 12, 2024 at 08:37:11AM +, Liuye wrote: >> >> I know that you said schedule_work is not NMI save, which is the >> >> first issue. Perhaps it can be fixed using irq_work_queue. But e

[Kgdb-bugreport] 答复: 答复: 答复: 答复: 答复: [PATCH] kdb: Fix the deadlock issue in KDB debugging.

>On Wed, Mar 13, 2024 at 01:22:17AM +0000, Liuye wrote: >> >On Tue, Mar 12, 2024 at 10:04:54AM +, Liuye wrote: >> >> >On Tue, Mar 12, 2024 at 08:37:11AM +, Liuye wrote: >> >> >> I know that you said schedule_work is not NMI save, which is the

[Kgdb-bugreport] 答复: [PATCH V3] kdb: Fix the deadlock issue in KDB debugging.

> The stack trace below shows an example of the problem. In this case > the master cpu is not running from NMI but it has parked the slave > CPUs using an NMI and the parked CPUs is holding spinlocks needed by > schedule_work(). Add description information > Signed-off-

[Kgdb-bugreport] 答复: [PATCH V4] kdb: Fix the deadlock issue in KDB debugging.

>On 21. 03. 24, 12:50, liu@h3c.com wrote: >> From: LiuYe >> >> Currently, if CONFIG_KDB_KEYBOARD is enabled, then kgdboc will attempt >> to use schedule_work() to provoke a keyboard reset when transitioning >> out of the debugger and back to normal oper

[Kgdb-bugreport] 答复: [PATCH V5] kdb: Fix the deadlock issue in KDB debugging.

>> Just need to postpone schedule_work to the slave CPU exiting the NMI context. >> >> irq_work will only respond to handle schedule_work after exiting the current >> interrupt context. >> >> When the master CPU exits the interrupt context, other CPUs will naturally >> exit the NMI context, so

Re: [Kgdb-bugreport] [PATCH V8] kdb: Fix the deadlock issue in KDB debugging.

>Wed, Apr 03, 2024 at 02:11:09PM +0800, liu@h3c.com kirjoitti: >> From: LiuYe >> >> Currently, if CONFIG_KDB_KEYBOARD is enabled, then kgdboc will >> attempt to use schedule_work() to provoke a keyboard reset when >> transitioning out of the debugger and back

[Kgdb-bugreport] 答复: [PATCH V7] kdb: Fix the deadlock issue in KDB debugging.

Hi Daniel, How about PATCH V7. Thanks. ___ Kgdb-bugreport mailing list Kgdb-bugreport@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kgdb-bugreport

[Kgdb-bugreport] 答复: [PATCH] kdb: Fix the deadlock issue in KDB debugging.

>On Wed, Feb 28, 2024 at 10:56:02AM +0800, LiuYe wrote: >> master cpu : After executing the go command, a deadlock occurs. >> slave cpu: may be performing thread migration, >> acquiring the running queue lock of master CPU. >> Then it was interru

[Kgdb-bugreport] [PATCH] kdb: Fix the deadlock issue in KDB debugging.

fy+0x35/0x70 [] notifier_call_chain+0x4a/0x70 [] notify_die+0x3d/0x50 [] do_int3+0x89/0x120 [] int3+0x44/0x80 Signed-off-by: LiuYe --- drivers/tty/serial/kgdboc.c | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/drivers/tty/serial/kgdboc.c b/drivers/tty/serial/kgdboc.c ind