Re: [LKP] [tty] 0b4f83d510: INFO:task_blocked_for_more_than#seconds

2018-09-10 Thread Dmitry Safonov
Hi Sergey, Jiri, On Mon, 2018-09-10 at 14:14 +0900, Sergey Senozhatsky wrote: > On (09/07/18 08:39), Jiri Slaby wrote: > > > [ 244.944070] > > > [ 244.944070] Showing all locks held in the system: > > > [ 244.945558] 1 lock held by khungtaskd/18: > > > [ 244.946495] #0: (ptrval)

Re: [LKP] [tty] 0b4f83d510: INFO:task_blocked_for_more_than#seconds

2018-09-10 Thread Dmitry Safonov
Hi Sergey, Jiri, On Mon, 2018-09-10 at 14:14 +0900, Sergey Senozhatsky wrote: > On (09/07/18 08:39), Jiri Slaby wrote: > > > [ 244.944070] > > > [ 244.944070] Showing all locks held in the system: > > > [ 244.945558] 1 lock held by khungtaskd/18: > > > [ 244.946495] #0: (ptrval)

Re: [LKP] [tty] 0b4f83d510: INFO:task_blocked_for_more_than#seconds

2018-09-09 Thread Sergey Senozhatsky
On (09/07/18 08:39), Jiri Slaby wrote: > > [ 244.944070] > > [ 244.944070] Showing all locks held in the system: > > [ 244.945558] 1 lock held by khungtaskd/18: > > [ 244.946495] #0: (ptrval) (rcu_read_lock){}, at: > > debug_show_all_locks+0x16/0x190 > > [ 244.948503] 2 locks

Re: [LKP] [tty] 0b4f83d510: INFO:task_blocked_for_more_than#seconds

2018-09-09 Thread Sergey Senozhatsky
On (09/07/18 08:39), Jiri Slaby wrote: > > [ 244.944070] > > [ 244.944070] Showing all locks held in the system: > > [ 244.945558] 1 lock held by khungtaskd/18: > > [ 244.946495] #0: (ptrval) (rcu_read_lock){}, at: > > debug_show_all_locks+0x16/0x190 > > [ 244.948503] 2 locks

Re: [LKP] [tty] 0b4f83d510: INFO:task_blocked_for_more_than#seconds

2018-09-07 Thread Dmitry Safonov
On Fri, 2018-09-07 at 08:39 +0200, Jiri Slaby wrote: > On 09/07/2018, 06:50 AM, kernel test robot wrote: > > FYI, we noticed the following commit (built with gcc-7): > > > > commit: 0b4f83d510f6fef6bb9da25f122c8d733d50516f ("[PATCH 2/4] tty: > > Hold tty_ldisc_lock() during tty_reopen()") > >

Re: [LKP] [tty] 0b4f83d510: INFO:task_blocked_for_more_than#seconds

2018-09-07 Thread Dmitry Safonov
On Fri, 2018-09-07 at 08:39 +0200, Jiri Slaby wrote: > On 09/07/2018, 06:50 AM, kernel test robot wrote: > > FYI, we noticed the following commit (built with gcc-7): > > > > commit: 0b4f83d510f6fef6bb9da25f122c8d733d50516f ("[PATCH 2/4] tty: > > Hold tty_ldisc_lock() during tty_reopen()") > >

Re: [LKP] [tty] 0b4f83d510: INFO:task_blocked_for_more_than#seconds

2018-09-07 Thread Jiri Slaby
On 09/07/2018, 06:50 AM, kernel test robot wrote: > FYI, we noticed the following commit (built with gcc-7): > > commit: 0b4f83d510f6fef6bb9da25f122c8d733d50516f ("[PATCH 2/4] tty: Hold > tty_ldisc_lock() during tty_reopen()") > url: >

Re: [LKP] [tty] 0b4f83d510: INFO:task_blocked_for_more_than#seconds

2018-09-07 Thread Jiri Slaby
On 09/07/2018, 06:50 AM, kernel test robot wrote: > FYI, we noticed the following commit (built with gcc-7): > > commit: 0b4f83d510f6fef6bb9da25f122c8d733d50516f ("[PATCH 2/4] tty: Hold > tty_ldisc_lock() during tty_reopen()") > url: >

[LKP] [tty] 0b4f83d510: INFO:task_blocked_for_more_than#seconds

2018-09-06 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-7): commit: 0b4f83d510f6fef6bb9da25f122c8d733d50516f ("[PATCH 2/4] tty: Hold tty_ldisc_lock() during tty_reopen()") url: https://github.com/0day-ci/linux/commits/Dmitry-Safonov/tty-Hold-write-ldisc-sem-in-tty_reopen/20180829-165618 base:

[LKP] [tty] 0b4f83d510: INFO:task_blocked_for_more_than#seconds

2018-09-06 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-7): commit: 0b4f83d510f6fef6bb9da25f122c8d733d50516f ("[PATCH 2/4] tty: Hold tty_ldisc_lock() during tty_reopen()") url: https://github.com/0day-ci/linux/commits/Dmitry-Safonov/tty-Hold-write-ldisc-sem-in-tty_reopen/20180829-165618 base: