From: Jarek Poplawski <jarkao2@gmail.com>
To: jamal <hadi@cyberus.ca>
Cc: Minoru Usui <usui@mxm.nes.nec.co.jp>,
netdev@vger.kernel.org, containers@lists.linux-foundation.org
Subject: Re: [BUG] net_cls: Panic occured when net_cls subsystem use
Date: Tue, 2 Jun 2009 23:10:31 +0200 [thread overview]
Message-ID: <20090602211031.GA2850@ami.dom.local> (raw)
In-Reply-To: <1243948587.3966.393.camel@dogo.mojatatu.com>
On Tue, Jun 02, 2009 at 09:16:27AM -0400, jamal wrote:
...
> Thanks for the courtesy.
> I note Dave already swallowed Minoru's patch; so lets move from there.
> Yes, there's a possibility of a regression - I (and so are you) are only
> recently evolved humans; we are not perfect... yet ;->
> So i would agree with Minoru testing your patch as plan B in case the
> applied one starts causing trouble.
> BTW, ok - here's a quick untested, uncompiled fix to the u32 classifier
> to fix the first rock (which you already worked around in your changes
> to the included patch). No rush to submit for now..
Thanks for your courtesy as well. Alas, I'm not sure I can fully
understand the current patch. You seem to redefine the ->get() method
usage, so it looks for handle only for configured tp's. It might be
right but I need more time to check this.
>
> On the second rock you threw so violently, after some reflection, I
> think it is ok to send a replace twice with different priorities.
> The second one will be added and the old not deleted, but if the user
> has chosen the correct priority, then things will work out just fine.
> And if they want they have to explicitly delete the one they dont want.
> It is also not illegal to do a "replace" for installing instead of
> "add".
>
> So the only other things left to do from this exercise are (no rush in
> any of them):
> a) remove all "buckets" from underneath other classifiers
> b) get consistency across all classifiers in usage of setup API
>
> If you want to do this - go ahead; else i plan on tackling it probably
> when stable 2.6.31 kicks in.
I definitely prefer you doing this and me asking "rude" questions.;-)
Cheers,
Jarek P.
> diff --git a/net/sched/cls_u32.c b/net/sched/cls_u32.c
> index 07372f6..5ad0b98 100644
> --- a/net/sched/cls_u32.c
> +++ b/net/sched/cls_u32.c
> @@ -249,6 +249,9 @@ static unsigned long u32_get(struct tcf_proto *tp, u32 handle)
> struct tc_u_hnode *ht;
> struct tc_u_common *tp_c = tp->data;
>
> + if (!tp_c)
> + return 0;
> +
> if (TC_U32_HTID(handle) == TC_U32_ROOT)
> ht = tp->root;
> else
> @@ -311,7 +314,6 @@ static int u32_init(struct tcf_proto *tp)
> root_ht->tp_c = tp_c;
>
> tp->root = root_ht;
> - tp->data = tp_c;
> return 0;
> }
>
> @@ -524,7 +526,7 @@ static int u32_change(struct tcf_proto *tp, unsigned long base, u32 handle,
> struct nlattr **tca,
> unsigned long *arg)
> {
> - struct tc_u_common *tp_c = tp->data;
> + struct tc_u_common *tp_c = tp->root->tp_c;
> struct tc_u_hnode *ht;
> struct tc_u_knode *n;
> struct tc_u32_sel *s;
> @@ -540,6 +542,7 @@ static int u32_change(struct tcf_proto *tp, unsigned long base, u32 handle,
> if (err < 0)
> return err;
>
> + tp->data = tp_c;
> if ((n = (struct tc_u_knode*)*arg) != NULL) {
> if (TC_U32_KEY(n->handle) == 0)
> return -EINVAL;
next prev parent reply other threads:[~2009-06-02 21:11 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-21 0:22 [BUG] net_cls: Panic occured when net_cls subsystem use Minoru Usui
2009-05-29 5:18 ` Minoru Usui
2009-05-29 7:48 ` Jarek Poplawski
2009-05-29 8:03 ` Jarek Poplawski
2009-05-29 10:22 ` Jarek Poplawski
[not found] ` <20090529102232.GA6279-8HppEYmqbBCE+EvaaNYduQ@public.gmane.org>
2009-05-29 13:15 ` jamal
2009-05-29 13:46 ` jamal
2009-05-29 13:54 ` jamal
2009-05-29 22:59 ` Jarek Poplawski
[not found] ` <20090529225929.GD2753-dUp/P3zyUuaNj9Bq2fkWzw@public.gmane.org>
2009-05-30 11:17 ` Minoru Usui
2009-05-30 11:45 ` Jarek Poplawski
2009-05-30 11:56 ` jamal
[not found] ` <1243684594.3966.89.camel-A00voryUPPswpNmlq7E/ZAC/G2K4zDHf@public.gmane.org>
2009-05-30 12:07 ` Jarek Poplawski
[not found] ` <20090530120750.GB3166-dUp/P3zyUuaNj9Bq2fkWzw@public.gmane.org>
2009-05-30 12:31 ` jamal
2009-05-30 12:45 ` Jarek Poplawski
2009-05-30 13:03 ` jamal
2009-05-30 13:20 ` Jarek Poplawski
2009-05-30 13:31 ` jamal
2009-05-30 14:00 ` Jarek Poplawski
[not found] ` <20090530140006.GE3166-dUp/P3zyUuaNj9Bq2fkWzw@public.gmane.org>
2009-05-30 22:38 ` Minoru Usui
2009-05-30 23:34 ` jamal
2009-05-31 1:45 ` Minoru Usui
2009-05-31 8:15 ` Jarek Poplawski
2009-05-30 23:08 ` jamal
[not found] ` <1243724933.3966.158.camel-A00voryUPPswpNmlq7E/ZAC/G2K4zDHf@public.gmane.org>
2009-05-31 7:55 ` Jarek Poplawski
2009-05-31 13:17 ` jamal
2009-05-31 20:33 ` Jarek Poplawski
2009-05-30 22:22 ` Minoru Usui
2009-05-30 23:13 ` jamal
2009-05-31 8:07 ` Jarek Poplawski
2009-05-30 11:50 ` jamal
2009-05-31 8:12 ` Jarek Poplawski
2009-05-31 13:24 ` jamal
2009-05-31 13:43 ` jamal
[not found] ` <1243777427.3966.243.camel-A00voryUPPswpNmlq7E/ZAC/G2K4zDHf@public.gmane.org>
2009-05-31 21:12 ` Jarek Poplawski
2009-05-31 19:55 ` Jarek Poplawski
[not found] ` <20090531195557.GA2777-dUp/P3zyUuaNj9Bq2fkWzw@public.gmane.org>
2009-05-31 23:40 ` jamal
2009-06-01 6:06 ` Jarek Poplawski
2009-06-01 13:03 ` jamal
2009-06-01 13:34 ` Minoru Usui
2009-06-01 20:49 ` Jarek Poplawski
2009-06-01 21:55 ` Jarek Poplawski
2009-06-01 22:06 ` jamal
[not found] ` <1243893963.3966.325.camel-A00voryUPPswpNmlq7E/ZAC/G2K4zDHf@public.gmane.org>
2009-06-02 6:26 ` Jarek Poplawski
2009-06-02 13:16 ` jamal
2009-06-02 21:10 ` Jarek Poplawski [this message]
2009-06-03 11:27 ` Jarek Poplawski
2009-06-10 11:58 ` jamal
2009-06-02 6:59 ` Minoru Usui
2009-06-02 7:24 ` Jarek Poplawski
2009-06-02 8:29 ` Minoru Usui
[not found] ` <20090602155919.da89c08e.usui-vEbCzmPPqHe45+QrQBaojngSJqDPrsil@public.gmane.org>
2009-06-02 13:19 ` jamal
2009-06-04 4:41 ` Minoru Usui
2009-06-04 6:34 ` Jarek Poplawski
2009-06-04 8:37 ` Jarek Poplawski
2009-06-01 5:25 ` Minoru Usui
2009-06-01 9:12 ` Minoru Usui
2009-06-08 6:39 ` Minoru Usui
2009-06-08 7:48 ` Jarek Poplawski
2009-06-09 0:02 ` Minoru Usui
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=20090602211031.GA2850@ami.dom.local \
--to=jarkao2@gmail.com \
--cc=containers@lists.linux-foundation.org \
--cc=hadi@cyberus.ca \
--cc=netdev@vger.kernel.org \
--cc=usui@mxm.nes.nec.co.jp \
/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).