From: Denys Fedoryshchenko <denys@visp.net.lb>
To: Jarek Poplawski <jarkao2@gmail.com>
Cc: David Miller <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: [PATCH]: Schedule correct qdisc in watchdog.
Date: Mon, 18 Aug 2008 15:45:29 +0300 [thread overview]
Message-ID: <200808181545.30146.denys@visp.net.lb> (raw)
In-Reply-To: <20080818113531.GB7158@ff.dom.local>
Patch applied, got another warning.
[ 413.646102]
[ 413.646102] =========================
[ 413.646102] [ BUG: held lock freed! ]
[ 413.646102] -------------------------
[ 413.646102] pppd/4105 is freeing memory f6fe6e00-f6fe6eff, with a lock
still held there!
[ 413.646102] (&qdisc_rx_lock){-+..}, at: [<c026e3ab>]
shutdown_scheduler_queue+0x1c/0x2e
[ 413.646102] 3 locks held by pppd/4105:
[ 413.646102] #0: (all_ppp_mutex){--..}, at: [<f8a671ae>]
ppp_shutdown_interface+0x17/0xb0 [ppp_generic]
[ 413.646102] #1: (rtnl_mutex){--..}, at: [<c026967a>] rtnl_lock+0xf/0x11
[ 413.647102] #2: (&qdisc_rx_lock){-+..}, at: [<c026e3ab>]
shutdown_scheduler_queue+0x1c/0x2e
[ 413.647102]
[ 413.647102] stack backtrace:
[ 413.647102] Pid: 4105, comm: pppd Not tainted
2.6.27-rc3-build-0031-12578-g96d2031-dirty #32
[ 413.647102] [<c02ba6f7>] ? printk+0xf/0x18
[ 413.647102] [<c013db8f>] debug_check_no_locks_freed+0xce/0xff
[ 413.647102] [<c01643ce>] kfree+0x78/0xc8
[ 413.647102] [<c026e38b>] ? qdisc_destroy+0x8c/0x90
[ 413.647102] [<c026e38b>] qdisc_destroy+0x8c/0x90
[ 413.647102] [<c026e3b2>] shutdown_scheduler_queue+0x23/0x2e
[ 413.647102] [<c026e3fa>] dev_shutdown+0x3d/0x59
[ 413.647102] [<c0262240>] rollback_registered+0x128/0x1b1
[ 413.647102] [<c02622fb>] unregister_netdevice+0x32/0x6e
[ 413.647102] [<c0262349>] unregister_netdev+0x12/0x1a
[ 413.647102] [<f8a671f3>] ppp_shutdown_interface+0x5c/0xb0 [ppp_generic]
[ 413.647102] [<f8a6742c>] ppp_release+0x2c/0x5a [ppp_generic]
[ 413.647102] [<c0167db8>] __fput+0x99/0x136
[ 413.647102] [<c0167e6c>] fput+0x17/0x19
[ 413.647102] [<c016593b>] filp_close+0x47/0x51
[ 413.647102] [<c01659b8>] sys_close+0x73/0xad
[ 413.647102] [<c0103861>] sysenter_do_call+0x12/0x35
[ 413.647102] =======================
On Monday 18 August 2008, Jarek Poplawski wrote:
next prev parent reply other threads:[~2008-08-18 12:46 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-18 8:39 [PATCH]: Schedule correct qdisc in watchdog David Miller
2008-08-18 9:10 ` Jarek Poplawski
2008-08-18 9:31 ` David Miller
2008-08-18 9:47 ` Jarek Poplawski
2008-08-18 10:10 ` David Miller
2008-08-18 10:35 ` Jarek Poplawski
2008-08-18 10:43 ` Jarek Poplawski
2008-08-18 11:04 ` Denys Fedoryshchenko
2008-08-18 11:20 ` Jarek Poplawski
2008-08-18 11:35 ` Jarek Poplawski
2008-08-18 12:45 ` Denys Fedoryshchenko [this message]
2008-08-18 12:58 ` Jarek Poplawski
2008-08-18 23:56 ` David Miller
2008-08-19 5:37 ` Jarek Poplawski
2008-08-19 5:39 ` David Miller
2008-08-19 5:42 ` Jarek Poplawski
2008-08-18 15:55 ` Jarek Poplawski
2008-08-18 18:05 ` Denys Fedoryshchenko
2008-08-19 3:54 ` David Miller
2008-08-19 6:59 ` Jarek Poplawski
2008-08-19 7:03 ` David Miller
2008-08-18 11:06 ` Jarek Poplawski
2008-08-19 3:51 ` David Miller
2008-08-19 4:08 ` David Miller
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=200808181545.30146.denys@visp.net.lb \
--to=denys@visp.net.lb \
--cc=davem@davemloft.net \
--cc=jarkao2@gmail.com \
--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 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).