An error occurred fetching the project authors.
- 12 Jun, 2004 1 commit
-
-
Arnaldo Carvalho de Melo authored
Move tcp sk_wmem_queued related functions to net/core/stream.c, will be used by other SOCK_STREAM protocols, starting with LLC. Also move the tcp_charge_skb to sock.h, for the same reasons. Signed-off-by:
Arnaldo Carvalho de Melo <acme@conectiva.com.br>
-
- 11 Jun, 2004 1 commit
-
-
Arnaldo Carvalho de Melo authored
Will be used by the poor cousins, starting with LLC. Signed-off-by:
Arnaldo Carvalho de Melo <acme@conectiva.com.br>
-
- 02 Jun, 2004 1 commit
-
-
Hideaki Yoshifuji authored
-
- 10 May, 2004 1 commit
-
-
Andrew Morton authored
From: john stultz <johnstul@us.ibm.com> This patch polishes up Tim Schmielau's (tim@physik3.uni-rostock.de) fix for jiffies_to_clock_t() and jiffies_64_to_clock_t(). The issues observed was w/ /proc output not matching up to wall time due to accumulated error caused by HZ not being exactly 1000 on i386 systems. The solution is to correct that error by using the more accurate TICK_NSEC in our calculation. Additionally, this patch corrects 3 warnings in the TCP layer uncovered by this change.
-
- 08 May, 2004 1 commit
-
-
James Morris authored
Under SELinux, and potentially other LSMs, we need to be able to distinguish between user sockets and kernel sockets. For SELinux specifically, kernel sockets need to be specially labeled during creation, then bypass access control checks (they are controlled by the kernel itself and not subject to SELinux mediation). This addresses a class of potential issues in SELinux where, for example, a TCP NFS session times out, then the kernel re-establishes an RPC connection upon further user activity. We do not want such kernel created sockets to be labeled with user security contexts. sock_create() and sock_create_kern() are wrapper functions, which seems semantically clearer to me than e.g. adding a flag to sock_create(). If you prefer the latter, then let me know. The patch also adds an argument to the LSM socket creation functions indicating whether the socket being created is a kernel socket or not.
-
- 01 May, 2004 1 commit
-
-
Herbert Xu authored
There is a bug in listening_get_first() which used by /proc/net/tcp* where it wasn't looping through all the sockets in each hash chain. This problem doesn't show up unless the first socket in a chain doesn't match the family that is being looked up. The following patch fixes this by getting rid of listening_get_first() altogether.
-
- 31 Mar, 2004 1 commit
-
-
Alexander Stohr authored
This cleans up a larger amount of superfluos ";;" statements in current Linux kernel sources by converting them to the regular single ";" statments. It seems to be a common problem that at the end of a line the semicolon key is producing an echo.
-
- 28 Mar, 2004 1 commit
-
-
Nivedita Singhvi authored
-
- 25 Jan, 2004 1 commit
-
-
Andrew Morton authored
-
- 01 Dec, 2003 1 commit
-
-
Hirofumi Ogawa authored
We need to initialize st->state in tcp_seq_start(). Otherwise tcp_seq_stop() is run with previous st->state, and it calls the unneeded unlock etc, causing a kernel crash.
-
- 29 Nov, 2003 1 commit
-
-
Hirofumi Ogawa authored
Forgotten initialization of st->state in tcp_seq_start().
-
- 08 Nov, 2003 1 commit
-
-
David S. Miller authored
-
- 01 Nov, 2003 1 commit
-
-
Hideaki Yoshifuji authored
-
- 27 Oct, 2003 1 commit
-
-
Hideaki Yoshifuji authored
-
- 26 Oct, 2003 1 commit
-
-
David S. Miller authored
I am still not sure that this change all by itself is enough to make us accept zero initial timestamps properly. Cset exclude: davem@nuts.ninka.net|ChangeSet|20031025060257|60993
-
- 24 Oct, 2003 1 commit
-
-
David S. Miller authored
-
- 15 Oct, 2003 1 commit
-
-
Arnaldo Carvalho de Melo authored
-
- 14 Oct, 2003 2 commits
-
-
Tim Shepard authored
-
Tim Shepard authored
-
- 08 Oct, 2003 1 commit
-
-
David S. Miller authored
-
- 27 Sep, 2003 1 commit
-
-
Arnaldo Carvalho de Melo authored
-
- 11 Sep, 2003 1 commit
-
-
Hideaki Yoshifuji authored
-
- 09 Sep, 2003 1 commit
-
-
Joe Perches authored
-
- 17 Aug, 2003 1 commit
-
-
David S. Miller authored
Based upon a patch from Herbert Xu (herbert@gondor.apana.org.au).
-
- 18 Jun, 2003 1 commit
-
-
Arnaldo Carvalho de Melo authored
With this we make it easier to write correct network families as less details need to be taken into account, as well in the current state we make the non-refcounting protocols (the ones still keeping deliver_to_old_ones in the tree) suck less. 8) Left a WARN_ON in sk_del_node_init for a while, so that we can catch cases where we're using __sock_put on a struct sock that has refcnt == 1, which is not the case for all the ones I tested.
-
- 17 Jun, 2003 1 commit
-
-
Arnaldo Carvalho de Melo authored
Move it to the protocols that we're using this pointers for other purposes than a list pointer as the name implies, namely tcp and sctp, where they are used as a pointer to the bind_hash. Shrink, struct sock, shrink! :-)
-
- 16 Jun, 2003 2 commits
-
-
Arnaldo Carvalho de Melo authored
-
Arnaldo Carvalho de Melo authored
-
- 14 Jun, 2003 1 commit
-
-
David S. Miller authored
-
- 04 Jun, 2003 1 commit
-
-
Arnaldo Carvalho de Melo authored
With this the data dependency is reduced to just making sure that the first member of both struct sock and struct tcp_tw_bucket are a struct sock_common. Also makes it easier to grep for struct sock and struct tcp_tw_bucket usage in the tree as all the members in those structs are prefixed, respectively, with sk_ and tw_, like struct inode (i_), struct block_device (bd_), etc. Checked namespace with make tags/ctags, just one colision with the macros for the struct sock members, with a wanrouter struct, fixed that s/sk_state/state_sk/g in the wanrouter struct. Checked as well if the names of the members in both structs collided with some macro, none found.
-
- 28 May, 2003 1 commit
-
-
David S. Miller authored
Bug discovered by Mandred Spraul.
-
- 25 May, 2003 1 commit
-
-
Hideaki Yoshifuji authored
-
- 21 May, 2003 1 commit
-
-
Hideaki Yoshifuji authored
-
- 15 May, 2003 1 commit
-
-
David S. Miller authored
-
- 14 May, 2003 1 commit
-
-
David S. Miller authored
-
- 13 May, 2003 1 commit
-
-
Arnaldo Carvalho de Melo authored
After all calls to tcp_tw_deschedule we had a call to tcp_timewait_kill, move it to the end of tcp_tw_deschedule and unexport tcp_timewait_kill, making it static.
-
- 10 May, 2003 1 commit
-
-
Hideaki Yoshifuji authored
-
- 03 May, 2003 1 commit
-
-
James Morris authored
- Consistent naming (i.e. jhash_xxx) - Reduces the 2&1 word variants to call jhash_3words() - Replaces __inline__ with inline.
-
- 02 May, 2003 1 commit
-
-
David S. Miller authored
Several hash table implementations in the networking were remotely exploitable. Remote attackers could launch attacks whereby, using carefully choosen forged source addresses, make every routing cache entry get hashed into the same hash chain. Netfilter's IP conntrack module and the TCP syn-queue implementation had identical vulnerabilities and have been fixed too. The choosen solution to the problem involved using Bob's Jenkins hash along with a randomly choosen input. For the ipv4 routing cache we take things one step further and periodically choose a new random secret. By default this happens every 10 minutes, but this is configurable by the user via sysctl knobs.
-
- 28 Apr, 2003 1 commit
-
-
Steven Cole authored
-