From: David Miller <davem@davemloft.net>
To: jhs@mojatatu.com
Cc: eric.dumazet@gmail.com, jiri@resnulli.us, netdev@vger.kernel.org,
xiyou.wangcong@gmail.com
Subject: Re: [PATCH net-next v4 1/2] net sched actions: dump more than TCA_ACT_MAX_PRIO actions per batch
Date: Thu, 20 Apr 2017 11:50:00 -0400 (EDT) [thread overview]
Message-ID: <20170420.115000.250335491542942036.davem@davemloft.net> (raw)
In-Reply-To: <48ec5026-38bf-ebfd-98e5-78c8cb1d24f5@mojatatu.com>
From: Jamal Hadi Salim <jhs@mojatatu.com>
Date: Thu, 20 Apr 2017 09:27:00 -0400
> The issue Jiri is bringing up is unrelated. He is talking about
> a bitmap and conflating it with a data structure. They are not
> the same issue.
Bitmaps can have the same exact problem as padding if we didn't code
it correctly.
The issue is _purely_, "did we check unused 'fields' and enforce them
to be a certain value"
If not, we lose, and can't use those "fields" in the future.
This rule applies whether you are speaking about padding or a bitmask.
next prev parent reply other threads:[~2017-04-20 15:50 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-19 11:57 [PATCH net-next v4 1/2] net sched actions: dump more than TCA_ACT_MAX_PRIO actions per batch Jamal Hadi Salim
2017-04-19 11:57 ` [PATCH net-next v4 2/2] net sched actions: add time filter for action dumping Jamal Hadi Salim
2017-04-19 12:53 ` Jiri Pirko
2017-04-19 13:11 ` Jamal Hadi Salim
2017-04-19 14:14 ` Jiri Pirko
2017-04-19 15:47 ` Jamal Hadi Salim
2017-04-19 15:55 ` Jiri Pirko
2017-04-19 12:36 ` [PATCH net-next v4 1/2] net sched actions: dump more than TCA_ACT_MAX_PRIO actions per batch Jiri Pirko
2017-04-19 12:55 ` Roman Mashak
2017-04-19 13:05 ` Jiri Pirko
2017-04-19 13:03 ` Jamal Hadi Salim
2017-04-19 13:13 ` Jiri Pirko
2017-04-19 15:37 ` Jamal Hadi Salim
2017-04-19 15:54 ` Jiri Pirko
2017-04-19 16:07 ` Jamal Hadi Salim
2017-04-19 16:17 ` Jiri Pirko
2017-04-20 10:42 ` Jamal Hadi Salim
2017-04-20 11:35 ` Jiri Pirko
2017-04-20 14:03 ` Jamal Hadi Salim
2017-04-20 12:18 ` Eric Dumazet
2017-04-20 13:27 ` Jamal Hadi Salim
2017-04-20 15:50 ` David Miller [this message]
2017-04-20 17:38 ` Jamal Hadi Salim
2017-04-20 17:58 ` David Miller
2017-04-21 10:36 ` Jamal Hadi Salim
2017-04-21 14:51 ` David Miller
2017-04-21 15:29 ` Jamal Hadi Salim
2017-04-21 15:38 ` David Miller
2017-04-21 15:55 ` Jamal Hadi Salim
2017-04-21 16:01 ` Jamal Hadi Salim
2017-04-21 16:12 ` David Miller
2017-04-21 18:11 ` Jamal Hadi Salim
2017-04-22 11:30 ` Jamal Hadi Salim
2017-04-24 9:27 ` Simon Horman
2017-04-24 12:54 ` Jamal Hadi Salim
2017-04-21 16:11 ` David Miller
2017-04-20 15:23 ` 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=20170420.115000.250335491542942036.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--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 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).