<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/include/net/compat.h, branch v2.6.16.9</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/include/net/compat.h?h=v2.6.16.9</id>
<link rel='self' href='https://git.amat.us/linux/atom/include/net/compat.h?h=v2.6.16.9'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2005-09-08T19:32:46Z</updated>
<entry>
<title>[NET]: Need struct sock forward decl in net/compat.h</title>
<updated>2005-09-08T19:32:46Z</updated>
<author>
<name>David S. Miller</name>
<email>davem@davemloft.net</email>
</author>
<published>2005-09-08T19:32:46Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=e50ef933e649a2b43aa10c8a60c491543b8b4c02'/>
<id>urn:sha1:e50ef933e649a2b43aa10c8a60c491543b8b4c02</id>
<content type='text'>
Else we get build failures like:

  CC      arch/sparc64/kernel/sparc64_ksyms.o
In file included from arch/sparc64/kernel/sparc64_ksyms.c:28:
include/net/compat.h:37: warning: "struct sock" declared inside parameter list
include/net/compat.h:37: warning: its scope is only this definition or declaration, which is probably not what you want

Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>[PATCH] Fix 32bit sendmsg() flaw</title>
<updated>2005-09-08T15:14:11Z</updated>
<author>
<name>Al Viro</name>
<email>viro@zeniv.linux.org.uk</email>
</author>
<published>2005-09-08T01:28:51Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=8920e8f94c44e31a73bdf923b04721e26e88cadd'/>
<id>urn:sha1:8920e8f94c44e31a73bdf923b04721e26e88cadd</id>
<content type='text'>
When we copy 32bit -&gt;msg_control contents to kernel, we walk the same
userland data twice without sanity checks on the second pass.

Second version of this patch: the original broke with 64-bit arches
running 32-bit-compat-mode executables doing sendmsg() syscalls with
unaligned CMSG data areas

Another thing is that we use kmalloc() to allocate and sock_kfree_s()
to free afterwards; less serious, but also needs fixing.

Signed-off-by: Al Viro &lt;viro@zeniv.linux.org.uk&gt;
Signed-off-by: David Woodhouse &lt;dwmw2@infradead.org&gt;
Signed-off-by: Chris Wright &lt;chrisw@osdl.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@osdl.org&gt;
</content>
</entry>
<entry>
<title>Linux-2.6.12-rc2</title>
<updated>2005-04-16T22:20:36Z</updated>
<author>
<name>Linus Torvalds</name>
<email>torvalds@ppc970.osdl.org</email>
</author>
<published>2005-04-16T22:20:36Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2'/>
<id>urn:sha1:1da177e4c3f41524e886b7f1b8a0c1fc7321cac2</id>
<content type='text'>
Initial git repository build. I'm not bothering with the full history,
even though we have it. We can create a separate "historical" git
archive of that later if we want to, and in the meantime it's about
3.2GB when imported into git - space that would just make the early
git days unnecessarily complicated, when we don't have a lot of good
infrastructure for it.

Let it rip!
</content>
</entry>
</feed>
