Re: [PATCH v2] irqchip/gicv3-its: fix some definitions of inner cacheability attributes

2019-04-15 Thread Yao HongBo
Hi Marc, sorry for ping you... What's your suggestion for this patch? I look forward to your reply. Thanks, Hongbo. On 4/8/2019 10:01 PM, Hongbo Yao wrote: > Some definitions of Inner Cacheability attibutes need to be corrected. > > Fixes: 8c828a535e29f ("irqchip/gicv3-its: Restore all cacheab

Re: [PATCH] time64: Avoid undefined behaviour in timespec64_add()

2019-02-25 Thread Yao HongBo
On 2/25/2019 12:53 PM, Deepa Dinamani wrote: > On Sun, Feb 24, 2019 at 7:13 PM Hongbo Yao wrote: >> >> I ran into this: >> >> = >> UBSAN: Undefined behaviour in ./include/linux/time64.h:70:2 >> sign

Re: possible deadlock in console_unlock

2019-02-18 Thread Yao HongBo
On 2/19/2019 9:32 AM, Sergey Senozhatsky wrote: > On (02/18/19 22:07), Yao HongBo wrote: >>>> 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-i

Re: possible deadlock in console_unlock

2019-02-18 Thread Yao HongBo
On 2/18/2019 1:46 PM, Sergey Senozhatsky wrote: > 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 harde

Re: possible deadlock in console_unlock

2019-02-18 Thread Yao HongBo
On 2/18/2019 1:46 PM, Sergey Senozhatsky wrote: > 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 harde

Re: possible deadlock in console_unlock

2019-02-16 Thread Yao HongBo
On 2/16/2019 3:46 PM, Sergey Senozhatsky wrote: > On (02/16/19 16:21), Sergey Senozhatsky wrote: >> On (02/16/19 14:36), Yao HongBo wrote: >>> hi, sergey: >>> >>> As shown in that link, https://lkml.org/lkml/2018/6/6/397 >>> >>> On the linux

possible deadlock in console_unlock

2019-02-15 Thread Yao HongBo
hi, sergey: As shown in that link, https://lkml.org/lkml/2018/6/6/397 On the linux kernel 5.0-rc6, Syzkaller also hit 'possible deadlock in console_unlock' bug for several times in my environment. This solution fixes things for me. Do you have a plan to submit patches to solve this problem. di

Re: [PATCH] nvme: fix out of bounds access in nvme_cqe_pending

2019-01-09 Thread Yao HongBo
On 1/10/2019 2:39 AM, Christoph Hellwig wrote: > On Mon, Jan 07, 2019 at 10:22:07AM +0800, Hongbo Yao wrote: >> There is an out of bounds array access in nvme_cqe_peding(). >> >> When enable irq_thread for nvme interrupt, there is racing between the >> nvmeq->cq_head updating and reading. > > J