On Wed, Sep 04, 2019 at 07:19:47PM +0900, Tetsuo Handa wrote:
> Ping? Syzbot is still reporting this problem.
It's in my queue, give me a chance :)
greg k-h
Ping? Syzbot is still reporting this problem.
On 2019/08/26 22:44, Tetsuo Handa wrote:
> On 2019/08/26 22:29, Greg Kroah-Hartman wrote:
>> On Mon, Aug 26, 2019 at 10:13:25PM +0900, Tetsuo Handa wrote:
>>> syzbot found that a thread can stall for minutes inside read_mem() or
>>> write_mem() after
On 2019/08/26 22:29, Greg Kroah-Hartman wrote:
> On Mon, Aug 26, 2019 at 10:13:25PM +0900, Tetsuo Handa wrote:
>> syzbot found that a thread can stall for minutes inside read_mem() or
>> write_mem() after that thread was killed by SIGKILL [1]. Reading from
>> iomem areas of /dev/mem can be slow,
On Mon, Aug 26, 2019 at 10:13:25PM +0900, Tetsuo Handa wrote:
> syzbot found that a thread can stall for minutes inside read_mem() or
> write_mem() after that thread was killed by SIGKILL [1]. Reading from
> iomem areas of /dev/mem can be slow, depending on the hardware.
> While reading 2GB at one
syzbot found that a thread can stall for minutes inside read_mem() or
write_mem() after that thread was killed by SIGKILL [1]. Reading from
iomem areas of /dev/mem can be slow, depending on the hardware.
While reading 2GB at one read() is legal, delaying termination of killed
thread for minutes is
5 matches
Mail list logo