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: <59184.1392750827@turing-police.cc.vt.edu>
Date:	Tue, 18 Feb 2014 14:13:47 -0500
From:	Valdis.Kletnieks@...edu
To:	Vladimir Davydov <vdavydov@...allels.com>
Cc:	LKML <linux-kernel@...r.kernel.org>, Jan Kara <jack@...e.cz>,
	Wu Fengguang <fengguang.wu@...el.com>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: Unkillable R-state process stuck in sendfile

On Mon, 17 Feb 2014 16:51:37 +0400, Vladimir Davydov said:

>         out_fd = eventfd(0, 0);
>         if (out_fd < 0)
>                 err(1, "eventfd");
>         ret = sendfile64(out_fd, in_fd, NULL, SIZE);

> I'm not sure if this is actually bad and should be fixed, but perhaps
> it's worth making do_generic_file_read() check for fatal signals pending
> and break the read loop if so?

Why do we even allow an eventfd to be fed to sendfile64 at all? What
does that even *mean*?

Content of type "application/pgp-signature" skipped

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ