lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <681500CE65202E47A192754B01DAB4673BE3D88235@SDE12.beckipc.net>
Date:   Fri, 27 Jul 2018 11:31:24 +0200
From:   André Pribil <a.pribil@...k-ipc.com>
To:     André Pribil <a.pribil@...k-ipc.com>,
        "netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: RE: Deadlock with restart_syscall()

> I've found this thread, where a similar issue with restart_syscall()
> has been reported:
> https://www.spinics.net/lists/netdev/msg415144.html

Found another old report about restart_syscall() producing a dead loop:
https://lists.gt.net/linux/kernel/2371438

I do not agree with the conclusion there that the user space should be 
to blame for this. I also see no ugly priority games in my scenario.

No one who wants to say anything about this?

Andre

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ