From: Alexey Dobriyan <adobriyan@parallels.com>
To: bugme-daemon@bugzilla.kernel.org
Cc: akpm@linux-foundation.org, kaber@trash.net, den@openvz.org,
netdev@vger.kernel.org, devzero@web.de
Subject: Re: [Bugme-new] [Bug 10737] New: pktgen procfs problem
Date: Mon, 19 May 2008 20:03:20 +0400 [thread overview]
Message-ID: <200805192003.21465.adobriyan@parallels.com> (raw)
> remove_proc_entry: removing non-empty directory 'net/pktgen', leaking at least 'kpktgend_1'
reproduced, and BTW, proc stuff is least of worries. It can also oops via
list_del corruption. prev->next should be ffff81007e8a5e70, but was 6b6b6b6b6b6b6b6b
kernel BUG at lib/list_debug.c:67!
:pktgen:pktgen_thread_worker+0x374/0x10b0
? autoremove_wake_function+0x0/0x40
? _spin_unlock_irqrestore+0x42/0x80
? :pktgen:pktgen_thread_worker+0x0/0x10b0
kthread+0x4d/0x80
child_rip+0xa/0x12
? restore_args+0x0/0x30
? kthread+0x0/0x80
? child_rip+0x0/0x12
RIP list_del+0x48/0x70
next reply other threads:[~2008-05-19 16:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-19 16:03 Alexey Dobriyan [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-05-20 21:57 [Bugme-new] [Bug 10737] New: pktgen procfs problem Alexey Dobriyan
2008-05-20 21:17 ` Robert Olsson
2008-05-19 22:21 Alexey Dobriyan
2008-05-19 22:45 ` Robert Olsson
2008-05-19 15:19 Alexey Dobriyan
[not found] <bug-10737-10286@http.bugzilla.kernel.org/>
2008-05-17 21:10 ` Andrew Morton
2008-05-18 1:39 ` Patrick McHardy
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
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=200805192003.21465.adobriyan@parallels.com \
--to=adobriyan@parallels.com \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=den@openvz.org \
--cc=devzero@web.de \
--cc=kaber@trash.net \
--cc=netdev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.