From: Hannes Frederic Sowa <hannes@stressinduktion.org>
To: netdev@vger.kernel.org, yoshfuji@linux-ipv6.org
Subject: Re: [PATCH RFC net-next] ipv6: avoid high order memory allocations for /proc/net/ipv6_route
Date: Thu, 22 Aug 2013 05:16:02 +0200 [thread overview]
Message-ID: <20130822031602.GA19269@order.stressinduktion.org> (raw)
In-Reply-To: <20130821175024.GA14419@order.stressinduktion.org>
On Wed, Aug 21, 2013 at 07:50:24PM +0200, Hannes Frederic Sowa wrote:
> I created this patch in a hurry while trying to get the rt6i_flags of
> the routing entries on a system with lots of routes (I later cleaned it
> up a bit).
>
> The current approach for dumping routes over netlink is to redump a tree
> as soon as the serialnumber on the nodes changes. Is this behavior more
> preferable as to just ignore the routes for that moment? I am in favour
> of not restarting the dump on /proc/net/ipv6_route.
Ok, I hit the same panics as Patrick once did
while some more stress testing this change
(http://permalink.gmane.org/gmane.linux.network/151391).
As I read this up, this was also the reason the serial checks where
introduced. It also tries to skip visited notes, so please void my
question above.
The reason is a disconnected fib6_node in FWS_U state trying to walk
up. I'll investigate if we can fix this up in the walker post-cleanup on
fib6_repair_tree/fib6_del_route (then we could also remove the serial
number checks on inet6_dump_fib) or I will make the appropriate serial
changes to this patch, too.
> +int ipv6_route_open(struct inode *inode, struct file *file)
> +{
> + return seq_open_net(inode, file, &ipv6_route_seq_ops,
> + sizeof(struct fib6_walker_t));
> +}
> +
sizeof(struct ipv6_route_iter) here, of course. :(
Greetings,
Hannes
next prev parent reply other threads:[~2013-08-22 3:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-21 17:50 [PATCH RFC net-next] ipv6: avoid high order memory allocations for /proc/net/ipv6_route Hannes Frederic Sowa
2013-08-22 3:16 ` Hannes Frederic Sowa [this message]
2013-08-27 18:24 ` Hannes Frederic Sowa
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=20130822031602.GA19269@order.stressinduktion.org \
--to=hannes@stressinduktion.org \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox