linux-kernel - Re: [PATCH] [RESEND] RFC: List per-process file descriptor consumption when hitting file-max

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]

Date:	Wed, 29 Jul 2009 17:12:48 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	alexander.shishckin@...il.com
Cc:	linux-fsdevel@...r.kernel.org, viro@...iv.linux.org.uk,
	linux-kernel@...r.kernel.org, alexander.shishckin@...il.com
Subject: Re: [PATCH] [RESEND] RFC: List per-process file descriptor
 consumption when hitting file-max

On Tue,  9 Jun 2009 12:01:11 +0300
alexander.shishckin@...il.com wrote:

> When a file descriptor limit is hit, it might be useful to see all the
> users to be able to identify those that leak descriptors.

Well... maybe.

There is no end to the amount of code which we could add to the kernel
to help userspace developers and administrators resolve userspace bugs.
But that doesn't mean that we should add all these things to the
kernel.

If there's some reason why the problem is particularly severe and
particularly hard to resolve by other means then sure, perhaps explicit
kernel support is justified.  But is that the case with this specific
userspace bug?

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/