linux-kernel - Re: 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-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 08 Oct 2008 17:28:57 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	eparis@...hat.com
Cc:	kkeil@...e.de, isdn4linux@...tserv.isdn4linux.de,
	linux-kernel@...r.kernel.org
Subject: Re: mISDN didn't define af_family_key_strings et al.

From: Eric Paris <eparis@...hat.com>
Date: Wed, 08 Oct 2008 20:27:29 -0400

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

This has been fixed in net-next-2.6 for a few weeks.

net/core/sock.c:
  "sk_lock-AF_RXRPC" , "sk_lock-AF_ISDN"     , "sk_lock-AF_PHONET"   ,
--
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/