From: Johannes Berg <johannes@sipsolutions.net>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: netdev@vger.kernel.org, bugme-daemon@bugzilla.kernel.org
Subject: Re: [Bugme-new] [Bug 12552] New: held lock freed in tcp
Date: Tue, 27 Jan 2009 19:57:12 +0100 [thread overview]
Message-ID: <1233082632.4455.8.camel@johannes.local> (raw)
In-Reply-To: <20090127101907.89833157.akpm@linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 980 bytes --]
On Tue, 2009-01-27 at 10:19 -0800, Andrew Morton wrote:
> (switched to email. Please respond via emailed reply-to-all, not via the
> bugzilla web interface).
>
> On Tue, 27 Jan 2009 09:59:06 -0800 (PST) bugme-daemon@bugzilla.kernel.org wrote:
>
> > http://bugzilla.kernel.org/show_bug.cgi?id=12552
> >
> > Summary: held lock freed in tcp
> > [ 598.850136] =========================
> > [ 598.850141] [ BUG: held lock freed! ]
> > [ 598.850143] -------------------------
> > [ 598.850147] swapper/0 is freeing memory ffff88007a389300-ffff88007a389c07,
> > with a lock still held there!
> > [ 598.850151] (&icsk->icsk_retransmit_timer){-+..}, at: [<ffffffff80252080>]
> > run_timer_softirq+0x110/0x290
> > [ 598.850163] 1 lock held by swapper/0:
> > [ 598.850165] #0: (&icsk->icsk_retransmit_timer){-+..}, at:
> > [<ffffffff80252080>] run_timer_softirq+0x110/0x290
Disregard, it's my own timer debugging code gone wrong.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2009-01-27 18:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-12552-10286@http.bugzilla.kernel.org/>
2009-01-27 18:19 ` [Bugme-new] [Bug 12552] New: held lock freed in tcp Andrew Morton
2009-01-27 18:57 ` Johannes Berg [this message]
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=1233082632.4455.8.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--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.