From: David Miller <davem@davemloft.net>
To: code@rkapl.cz
Cc: netdev@vger.kernel.org, jiri@resnulli.us,
xiyou.wangcong@gmail.com, jbenc@redhat.com
Subject: Re: [PATCH] net: sched: report if filter is too large to dump
Date: Mon, 19 Feb 2018 14:08:15 -0500 (EST) [thread overview]
Message-ID: <20180219.140815.1665340266913500299.davem@davemloft.net> (raw)
In-Reply-To: <20180218221047.27678-1-code@rkapl.cz>
From: Roman Kapl <code@rkapl.cz>
Date: Sun, 18 Feb 2018 23:10:47 +0100
> So far, if the filter was too large to fit in the allocated skb, the
> kernel did not return any error and stopped dumping. Modify the dumper
> so that it returns -ENOMSG when a filter fails to dump and it is the
> first filter in the skb. If we are not first, we will get a next chance
> with more room.
I don't see -ENOMSG used in your code, maybe you meant -EMSGSIZE.
> I understand this is pretty near to being an API change, but the
> original design (silent truncation) can be considered a bug.
>
> Note: The error case can happen pretty easily if you create a filter
> with 32 actions and have 4kb pages. Also recent versions of iproute try
> to be clever with their buffer allocation size, which in turn leads to
> smaller SKBs in kernel.
>
> Signed-off-by: Roman Kapl <code@rkapl.cz>
Please do a little bit of research to seeh ow other subsystems
handle this situation, we should match whatever they do to be
consistent system wide with netlink.
You have to respin this patch to fix up the commit message anyways :-)
Thanks.
prev parent reply other threads:[~2018-02-19 19:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-18 22:10 [PATCH] net: sched: report if filter is too large to dump Roman Kapl
2018-02-19 19:08 ` David Miller [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=20180219.140815.1665340266913500299.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=code@rkapl.cz \
--cc=jbenc@redhat.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).