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>] [day] [month] [year] [list]
Date:   Mon, 20 Jul 2020 18:52:37 +0800
From:   Feng Li <lifeng1519@...il.com>
To:     linux-kernel <linux-kernel@...r.kernel.org>,
        Ming Lei <ming.lei@...hat.com>,
        linux-block <linux-block@...r.kernel.org>
Subject: [Question] About IO timeout and hang

Hi Experts,

Consider accessing a "bad" disk, if the user process submits a
'read/write' request to the kernel through libaio,
and the kernel doesn't return the IO, because the underlay disk is
bad, and IO is stuck for a long time.

When the IO is a 'read', the user-space process has its own timeout
policy, and find this IO has timeout-ed, then is it safe
to free the io buffer before IO error return?
If the user-space doesn't free the buffer and use this buffer as
another read request, for example, read from another health disk,
and if at this time the bad disk response the IO,
will the buffer be corrupted by the before 'read' request?

Could anyone help me clarify this concern?

Thanks in advance.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ