linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: alexander.shishckin@gmail.com
Cc: linux-fsdevel@vger.kernel.org, viro@zeniv.linux.org.uk,
	linux-kernel@vger.kernel.org, alexander.shishckin@gmail.com
Subject: Re: [PATCH] [RESEND] RFC: List per-process file descriptor consumption when hitting file-max
Date: Wed, 29 Jul 2009 17:12:48 -0700	[thread overview]
Message-ID: <20090729171248.764570f2.akpm@linux-foundation.org> (raw)
In-Reply-To: <1244538071-992-1-git-send-email-alexander.shishckin@gmail.com>

On Tue,  9 Jun 2009 12:01:11 +0300
alexander.shishckin@gmail.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?



  reply	other threads:[~2009-07-30  0:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-09  9:01 [PATCH] [RESEND] RFC: List per-process file descriptor consumption when hitting file-max alexander.shishckin
2009-07-30  0:12 ` Andrew Morton [this message]
2009-10-11 12:08   ` Alexander Shishkin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090729171248.764570f2.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=alexander.shishckin@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).