netdev - using KERN

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: <556445368AFA1C438794ABDA8901891C0A5A07D6@USA0300MS03.na.xerox.net>
Date:	Wed, 14 Jan 2009 16:28:28 -0500
From:	"Leisner, Martin" <Martin.Leisner@...ox.com>
To:	<netdev@...r.kernel.org>
Cc:	<martyleisner@...oo.com>
Subject: using KERN_ERR in IPv6

We're using 2.6.20 (but its also in 2.6.28).

In ipv6/ndisc.c:ndisc_router_discover() (cut and pasted from 2.6.20)
         if (rt == NULL && lifetime) {
                ND_PRINTK3(KERN_DEBUG
                           "ICMPv6 RA: adding default router.\n");

                rt = rt6_add_dflt_router(&skb->nh.ipv6h->saddr,
skb->dev, pref);
                if (rt == NULL) {
                        ND_PRINTK0(KERN_ERR
                                   "ICMPv6 RA: %s() failed to add
default route.\n",
                                   __FUNCTION__);
                        in6_dev_put(in6_dev);
                        return;
                }

                neigh = rt->rt6i_nexthop;
                if (neigh == NULL) {
                        ND_PRINTK0(KERN_ERR
                                   "ICMPv6 RA: %s() got default router
without neighbour.\n",
                                   __FUNCTION__);
                        dst_release(&rt->u.dst);
                        in6_dev_put(in6_dev);
                        return;
                }

My understanding is when running again a Microsoft 2003 server, it has a
bug  which excites  the message "failed to add default route" which is
normally echoed to the console which is quite cumbersome.

With Microsoft 2007 servers, the problem goes away.

But why would a protocol problem be a KERN_ERR (maybe KERN_INFO?)

Comments?

marty


--
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