From: Jarek Poplawski <jarkao2@gmail.com>
To: Denys Fedoryshchenko <denys@visp.net.lb>
Cc: netdev@vger.kernel.org
Subject: Re: panic 2.6.27-rc3-git2, qdisc_dequeue_head
Date: Sun, 17 Aug 2008 23:47:52 +0200 [thread overview]
Message-ID: <20080817214752.GA2546@ami.dom.local> (raw)
In-Reply-To: <200808172236.17857.denys@visp.net.lb>
On Sun, Aug 17, 2008 at 10:36:17PM +0300, Denys Fedoryshchenko wrote:
> I am lost in patches :-)
> When you will be back, let me know if order and set of patches is correct.
> Here is what i am using:
>
> http://www.nuclearcat.com/patches/00-prevfixes1.patch
> http://www.nuclearcat.com/patches/00-prevfixes2.patch
> http://www.nuclearcat.com/patches/01-take3.patch
> http://www.nuclearcat.com/patches/02-fix1.patch
> http://www.nuclearcat.com/patches/03-fix_patch_2.patch
>
> And thanks for your help!
> I cannot take risk and put to wide production, since it is crashing sometimes,
> but i guess in few days we can make it ready for production.
>
OK, so please try to test with all these patches above plus one new
patch below.
Thanks,
Jarek P.
(04-fix_patch_3.patch)
---
net/sched/sch_api.c | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/net/sched/sch_api.c b/net/sched/sch_api.c
index c25465e..c8dc72e 100644
--- a/net/sched/sch_api.c
+++ b/net/sched/sch_api.c
@@ -638,9 +638,9 @@ static void notify_and_destroy(struct sk_buff *skb, struct nlmsghdr *n, u32 clid
qdisc_notify(skb, n, clid, old, new);
if (old) {
- spin_lock_bh(&old->q.lock);
+ sch_tree_lock(old);
qdisc_destroy(old);
- spin_unlock_bh(&old->q.lock);
+ sch_tree_unlock(old);
}
}
next prev parent reply other threads:[~2008-08-17 21:47 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-15 19:09 panic 2.6.27-rc3-git2, qdisc_dequeue_head Denys Fedoryshchenko
2008-08-15 20:16 ` Jarek Poplawski
2008-08-15 20:36 ` Denys Fedoryshchenko
2008-08-15 20:54 ` Denys Fedoryshchenko
2008-08-16 8:55 ` Jarek Poplawski
2008-08-16 9:13 ` Jarek Poplawski
2008-08-16 10:03 ` Denys Fedoryshchenko
2008-08-16 10:05 ` Denys Fedoryshchenko
2008-08-16 12:27 ` Jarek Poplawski
2008-08-16 12:24 ` Denys Fedoryshchenko
2008-08-16 12:34 ` Jarek Poplawski
2008-08-16 13:13 ` Denys Fedoryshchenko
2008-08-16 14:27 ` Jarek Poplawski
2008-08-16 15:28 ` Denys Fedoryshchenko
2008-08-16 15:59 ` Jarek Poplawski
2008-08-16 18:15 ` Denys Fedoryshchenko
2008-08-16 18:52 ` Jarek Poplawski
2008-08-16 19:22 ` Denys Fedoryshchenko
2008-08-16 19:47 ` Jarek Poplawski
2008-08-17 9:02 ` Denys Fedoryshchenko
2008-08-17 9:34 ` Jarek Poplawski
2008-08-17 9:35 ` Denys Fedoryshchenko
2008-08-17 9:52 ` Jarek Poplawski
2008-08-17 10:01 ` Denys Fedoryshchenko
2008-08-17 10:31 ` Jarek Poplawski
2008-08-17 10:55 ` Jarek Poplawski
2008-08-17 12:06 ` Denys Fedoryshchenko
2008-08-17 12:18 ` Denys Fedoryshchenko
2008-08-17 12:38 ` Jarek Poplawski
2008-08-17 12:50 ` Denys Fedoryshchenko
2008-08-17 13:03 ` Denys Fedoryshchenko
2008-08-17 13:36 ` Jarek Poplawski
2008-08-17 19:36 ` Denys Fedoryshchenko
2008-08-17 21:47 ` Jarek Poplawski [this message]
2008-08-17 22:02 ` David Miller
2008-08-17 22:21 ` Denys Fedoryshchenko
2008-08-17 22:32 ` Jarek Poplawski
2008-08-17 13:16 ` Jarek Poplawski
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=20080817214752.GA2546@ami.dom.local \
--to=jarkao2@gmail.com \
--cc=denys@visp.net.lb \
--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.