From: Patrick McHardy <kaber@trash.net>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: netdev@vger.kernel.org, bugme-daemon@bugzilla.kernel.org,
devzero@web.de, Robert Olsson <robert.olsson@its.uu.se>,
"Denis V. Lunev" <den@openvz.org>
Subject: Re: [Bugme-new] [Bug 10737] New: pktgen procfs problem
Date: Sun, 18 May 2008 03:39:42 +0200 [thread overview]
Message-ID: <482F88DE.8090508@trash.net> (raw)
In-Reply-To: <20080517141036.d8f3c768.akpm@linux-foundation.org>
Andrew Morton wrote:
> (switched to email. Please respond via emailed reply-to-all, not via the
> bugzilla web interface).
>
> On Sat, 17 May 2008 13:59:25 -0700 (PDT) bugme-daemon@bugzilla.kernel.org wrote:
>
>
>> http://bugzilla.kernel.org/show_bug.cgi?id=10737
>>
>> Summary: pktgen procfs problem
>> Product: Networking
>> Version: 2.5
>> KernelVersion: 2.6.26-rc2
>> Platform: All
>> OS/Version: Linux
>> Tree: Mainline
>> Status: NEW
>> Severity: normal
>> Priority: P1
>> Component: Other
>> AssignedTo: acme@ghostprotocols.net
>> ReportedBy: devzero@web.de
>>
>>
>> Latest working kernel version: n/a
>> Earliest failing kernel version: 2.6.26-rc2
>> Distribution: suse 10.1
>> Hardware Environment: p4 + gigabyte i915g MoBo
>> Software Environment:
>> Problem Description:
>> pktgen module ocaasional seems to leak procfs entry
>>
>> May 18 00:00:34 test kernel: [ 2663.373955] pktgen v2.69: Packet Generator for
>> packet performance testing.
>> May 18 00:00:34 test kernel: [ 2663.384819] remove_proc_entry: removing
>> non-empty directory 'net/pktgen', leaking at least 'kpktgend_1'
>>
>
> ^^
>
> Possibly we were always leaking this procfs entry, and newly-added
> procfs diagnostics are now detecting it.
>
I've been looking into the same problem, without much success so
far. The problem appears to affect any /proc/net file, but not
files outside of /proc/net, so I'm guessing its net-ns related.
A testcase found by Ben Greear is opening the file multiple times:
# /tmp/open /proc/net/kpktgen_0
=> refcnt goes to 1
^C
=> refcnt goes to 0
Without ^C and opening the file a second time:
# /tmp/open /proc/net/kpktgen_0
=> refcnt goes to 2 (sometimes also 11)
^C
=> refcnt stays at previous value.
The refcnt even leaks if the file can't be successfully opened,
for example because of lacking permissions.
next prev parent reply other threads:[~2008-05-18 1:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-10737-10286@http.bugzilla.kernel.org/>
2008-05-17 21:10 ` [Bugme-new] [Bug 10737] New: pktgen procfs problem Andrew Morton
2008-05-18 1:39 ` Patrick McHardy [this message]
2008-05-18 4:56 ` Andrew Morton
2008-05-18 12:06 ` Patrick McHardy
2008-05-18 13:24 ` Patrick McHardy
2008-05-18 15:31 ` Patrick McHardy
2008-05-19 7:54 ` Denis V. Lunev
2008-05-19 10:34 ` Patrick McHardy
2008-05-20 0:26 ` Ben Greear
2008-05-20 1:14 ` Eric W. Biederman
2008-05-20 8:25 ` Robert Olsson
2008-05-19 21:34 ` Eric W. Biederman
2008-05-19 22:19 ` Ben Greear
2008-05-19 15:19 Alexey Dobriyan
-- strict thread matches above, loose matches on Subject: below --
2008-05-19 16:03 Alexey Dobriyan
2008-05-19 22:21 Alexey Dobriyan
2008-05-19 22:45 ` Robert Olsson
2008-05-20 21:57 Alexey Dobriyan
2008-05-20 21:17 ` Robert Olsson
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=482F88DE.8090508@trash.net \
--to=kaber@trash.net \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=den@openvz.org \
--cc=devzero@web.de \
--cc=netdev@vger.kernel.org \
--cc=robert.olsson@its.uu.se \
/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).