[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1211183642.9966.6.camel@iris.sw.ru>
Date: Mon, 19 May 2008 11:54:02 +0400
From: "Denis V. Lunev" <den@...nvz.org>
To: Patrick McHardy <kaber@...sh.net>
Cc: Andrew Morton <akpm@...ux-foundation.org>, netdev@...r.kernel.org,
bugme-daemon@...zilla.kernel.org, devzero@....de,
Robert Olsson <robert.olsson@....uu.se>,
Pavel Emelyanov <xemul@...nvz.org>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
Ben Greear <greearb@...delatech.com>
Subject: Re: [Bugme-new] [Bug 10737] New: pktgen procfs problem
On Sun, 2008-05-18 at 17:31 +0200, Patrick McHardy wrote:
> Patrick McHardy wrote:
> >>>> 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.
> >>>>
> >>>
> >>> urgh. Is any of this known to be post-2.6.25?
> >>>
> >>
> >> 2.6.25 is also affected. I don't know about earlier kernels.
> >
> > Some more information: the problem seems to occur only if
> > the file is opened by two different processes.
> >
> > I'm starting a bisection now.
>
>
> git-bisect identified e9720acd ([NET]: Make /proc/net a symlink
> on /proc/self/net (v3)) as the guilty commit. I couldn't find
> the problem in that commit, so someone with a better understanding
> of how this is supposed to work should look into it.
could you consider this preliminary patch? It fixes the problem for me
and Pavel agrees with it.
The problem is that module_get is called for each file opening while
module_put is called only when /proc inode is destroyed. So, lets put
module counter if we are dealing with already initialised inode.
View attachment "diff-procinode-count" of type "text/x-patch" (325 bytes)
Powered by blists - more mailing lists