From: rasto rickardt <rickardt@profinet.sk>
To: linux-kernel@vger.kernel.org
Subject: lockd bug still not fixed?
Date: Sun, 19 May 2002 19:43:13 +0200 [thread overview]
Message-ID: <3CE7E431.4070303@profinet.sk> (raw)
There is an inode leak in lockd in 2.2.19, caused by a reference
counting problem as mentioned in
http://lists.insecure.org/linux-kernel/2000/Sep/0129.html
i have this on 2.2.19 SMP kernel
kernel: grow_inodes: inode-max limit reached in syslog
i searched web and mailing lists if this issue was fixed in 2.4 but i
did not found any reasonable mention about it.
can someone provide me more information about this?
many thanks
rasto
--
rasto rickardt <rickardt@profinet.sk>
Prof-I-NeT SysAdmin
www.profinet.sk
www.host.sk
reply other threads:[~2002-05-19 17:43 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=3CE7E431.4070303@profinet.sk \
--to=rickardt@profinet.sk \
--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