netdev - Re: [PATCH 4/4][SCTP]: Change adaption -> adaptation as per the latest API draft.

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]

Message-Id: <1166134936.13207.30.camel@w-sridhar2.beaverton.ibm.com>
Date:	Thu, 14 Dec 2006 14:22:16 -0800
From:	Sridhar Samudrala <sri@...ibm.com>
To:	David Miller <davem@...emloft.net>
Cc:	netdev@...r.kernel.org, lksctp-developers@...ts.sourceforge.net
Subject: Re: [PATCH 4/4][SCTP]: Change adaption -> adaptation as per the
	latest API draft.

On Wed, 2006-12-13 at 18:03 -0800, David Miller wrote:
> From: Sridhar Samudrala <sri@...ibm.com>
> Date: Wed, 13 Dec 2006 17:38:52 -0800
> 
> > These parameters are not used by user-space apps. They define the
> > parameters used by the protocol in SCTP headers that go on wire.
> 
> There is no __KERNEL__ ifdef protection for these defines,
> and the linux/sctp.h header is exported to userspace via
> include/linux/Kbuild, therefore the interface is exposed to
> userspace and you cannot break it.

I didn't know that all the files under include/linux are exported
to userspace.
AFAIK, i don't think there are any SCTP apps that use this file.

But if you say that we shouldn't remove any of the APIs in 
linux/sctp.h, i am OK with keeping the existing ones and adding
new ones with the changed name.

Now that 2.6.20-rc1 is out, should i wait until 2.6.21 tree to open
for re-submission or is there a window still open for 2.6.20?

Thanks
Sridhar

-
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