netdev - Routing cache design question

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-Id: <657981400248936@web28j.yandex.ru>
Date:	Fri, 16 May 2014 18:02:16 +0400
From:	Oleg A Arkhangelsky <sysoleg@...dex.ru>
To:	netdev <netdev@...r.kernel.org>
Subject: Routing cache design question

Hello,

Currently I'm studying routing cache on relatively old, pre- 3.6 kernel. I can't
understand why in some situations we don't just invalidate routing cache with
new genid, but perform explicit full cleanup of all entries? Yes, I understand
that this is absolutely necessary when we unregister network device, otherwise
kernel will spin inside netdev_wait_allrefs() till rt_check_expire() kill all
entries referencing this device. That's too long.

But why is this behavior necessary after, for example, device MTU change, or
physical link up/down (NETDEV_CHANGE) event?

Thank you!

--
wbr, Oleg.

"Anarchy is about taking complete responsibility for yourself."
      Alan Moore.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html