From: John Fastabend <john.fastabend@gmail.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: xiyou.wangcong@gmail.com, davem@davemloft.net,
netdev@vger.kernel.org, jhs@mojatatu.com
Subject: Re: [net-next PATCH v2] net: sched: cls_u32: rcu can not be last node
Date: Wed, 17 Sep 2014 11:03:42 -0700 [thread overview]
Message-ID: <5419CCFE.8030906@gmail.com> (raw)
In-Reply-To: <1410976082.7106.239.camel@edumazet-glaptop2.roam.corp.google.com>
On 09/17/2014 10:48 AM, Eric Dumazet wrote:
> On Wed, 2014-09-17 at 10:31 -0700, John Fastabend wrote:
>> tc_u32_sel 'sel' in tc_u_knode expects to be the last element in the
>> structure and pads the structure with tc_u32_key fields for each key.
>>
>> kzalloc(sizeof(*n) + s->nkeys*sizeof(struct tc_u32_key), GFP_KERNEL)
>>
>> CC: Eric Dumazet <edumazet@google.com>
>> Signed-off-by: John Fastabend <john.r.fastabend@intel.com>
>> ---
>> net/sched/cls_u32.c | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/net/sched/cls_u32.c b/net/sched/cls_u32.c
>> index eceeb04..8462132 100644
>> --- a/net/sched/cls_u32.c
>> +++ b/net/sched/cls_u32.c
>> @@ -64,8 +64,9 @@ struct tc_u_knode {
>> u32 __percpu *pcpu_success;
>> #endif
>> struct tcf_proto *tp;
>> - struct tc_u32_sel sel;
>> struct rcu_head rcu;
>> + struct tc_u32_sel sel;
>> + /* tc_u32_keys allocated at end of structure */
>> };
>>
>> struct tc_u_hnode {
>
> Sorry to be picky, but comment should be before 'sel' or at same line.
no problem lets get it right, I'll post a v3 now and write a better
comment.
>
> It should mention that 'sel' MUST be last field.
>
> Thanks !
>
--
John Fastabend Intel Corporation
prev parent reply other threads:[~2014-09-17 18:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-17 17:31 [net-next PATCH v2] net: sched: cls_u32: rcu can not be last node John Fastabend
2014-09-17 17:48 ` Eric Dumazet
2014-09-17 18:03 ` John Fastabend [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=5419CCFE.8030906@gmail.com \
--to=john.fastabend@gmail.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=jhs@mojatatu.com \
--cc=netdev@vger.kernel.org \
--cc=xiyou.wangcong@gmail.com \
/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.