linux-kernel - mISDN didn't define af_family_key

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>] [thread-next>] [day] [month] [year] [list]

Message-Id: <1223512049.2952.8.camel@localhost.localdomain>
Date:	Wed, 08 Oct 2008 20:27:29 -0400
From:	Eric Paris <eparis@...hat.com>
To:	kkeil@...e.de
Cc:	isdn4linux@...tserv.isdn4linux.de, linux-kernel@...r.kernel.org,
	davem@...emloft.net
Subject: mISDN didn't define af_family_key_strings et al.

I see that recently AF_ISDN was added to the kernel but I don't see them
having updated af_family_key_strings[] found in net/core/sock.c.  I'm
adding a new one myself and caught a NULL entry toward the end of the
array.  My assumption is that isdn is using the sk_lock-AF_MAX entry
instead of their own.

As an aside it was nice having such a clean explosion when I didn't add
my own.  Are the AF_MAX entries in those arrays really needed?  If we
dropped it altogether would others (like myself and the isdn people) who
forgot to add their own get nice explosions with no other problems?

-Eric

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/