mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Martin J. Bligh" <mbligh@aracnet.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: [Bug 600] New: File locking memory leak
Date: Fri, 18 Apr 2003 07:30:54 -0700	[thread overview]
Message-ID: <23360000.1050676254@[10.10.2.4]> (raw)

I'll forward this one out as a plea for more information / testers ;-)

M.

---------- Forwarded Message ----------

http://bugme.osdl.org/show_bug.cgi?id=600

           Summary: File locking memory leak
    Kernel Version: many
            Status: NEW
          Severity: high
             Owner: willy@debian.org
         Submitter: willy@debian.org


Problem Description:

Some people have reported to me that the file_lock_cache grows virtually
without bound.  I haven't been able to reproduce the problem yet.  I'm
filing this bug here to track the problem.

I suspect it depends on workload.  First problem will be to track down what
type of lock it is; that'll give me some clue as to which of the three
independent implementations in the file locking code is leaking locks.

Steps to reproduce:


                 reply	other threads:[~2003-04-18 14:52 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='23360000.1050676254@[10.10.2.4]' \
    --to=mbligh@aracnet.com \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®