From: Thomas Jarosch <thomas.jarosch@intra2net.com>
To: Roland Dreier <roland@kernel.org>
Cc: netdev@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH 3.19 and earlier] fib_rules: Fix dump_rules() not to exit early
Date: Fri, 09 Oct 2015 16:33:56 +0200 [thread overview]
Message-ID: <3579656.ISPokoglEp@storm> (raw)
In-Reply-To: <1444066168-5566-1-git-send-email-roland@kernel.org>
Hi Roland,
On Monday, 5. October 2015 10:29:28 Roland Dreier wrote:
> From: Roland Dreier <roland@purestorage.com>
>
> Backports of 41fc014332d9 ("fib_rules: fix fib rule dumps across
> multiple skbs") introduced a regression in "ip rule show" - it ends up
> dumping the first rule over and over and never exiting, because 3.19
> and earlier are missing commit 053c095a82cf ("netlink: make
> nlmsg_end() and genlmsg_end() void"), so fib_nl_fill_rule() ends up
> returning skb->len (i.e. > 0) in the success case.
>
> Fix this by checking the return code for < 0 instead of != 0.
thanks for this fix. You just saved me an afternoon of bisecting :)
I can confirm that this fixes the mentioned issue introduced in 3.14.54.
We have an automated ipsec VPN test that failed after the upgrade:
The "ip rule list" command was hanging forever.
Cheers,
Thomas
next prev parent reply other threads:[~2015-10-09 14:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-05 17:29 [PATCH 3.19 and earlier] fib_rules: Fix dump_rules() not to exit early Roland Dreier
2015-10-05 21:50 ` Jiri Slaby
2015-10-08 12:50 ` Ben Hutchings
2015-10-09 14:33 ` Thomas Jarosch [this message]
2015-10-18 0:12 ` Greg KH
2015-10-18 0:34 ` Patch "fib_rules: Fix dump_rules() not to exit early" has been added to the 3.14-stable tree gregkh
2015-10-18 0:51 ` Patch "fib_rules: Fix dump_rules() not to exit early" has been added to the 3.10-stable tree gregkh
2015-10-19 10:24 ` [PATCH 3.19 and earlier] fib_rules: Fix dump_rules() not to exit early Luis Henriques
2015-10-19 10:24 ` Luis Henriques
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=3579656.ISPokoglEp@storm \
--to=thomas.jarosch@intra2net.com \
--cc=netdev@vger.kernel.org \
--cc=roland@kernel.org \
--cc=stable@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.