1. 04 1月, 2006 7 次提交
    • A
      [IPV6]: Introduce inet6_timewait_sock · 0fa1a53e
      Arnaldo Carvalho de Melo 提交于
      Out of tcp6_timewait_sock, that now is just an aggregation of
      inet_timewait_sock and inet6_timewait_sock, using tw_ipv6_offset in struct
      inet_timewait_sock, that is common to the IPv6 transport protocols that use
      timewait sockets, like DCCP and TCP.
      
      tw_ipv6_offset plays the struct inet_sock pinfo6 role, i.e. for the generic
      code to find the IPv6 area in a timewait sock.
      Signed-off-by: NArnaldo Carvalho de Melo <acme@mandriva.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      0fa1a53e
    • A
      [IPV6]: Generalise some functions · b9750ce1
      Arnaldo Carvalho de Melo 提交于
      Using sk->sk_protocol instead of IPPROTO_TCP.
      
      Will be used by DCCPv6 in the next changesets.
      Signed-off-by: NArnaldo Carvalho de Melo <acme@mandriva.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      b9750ce1
    • H
      [IP]: Simplify and consolidate MSG_PEEK error handling · 3305b80c
      Herbert Xu 提交于
      When a packet is obtained from skb_recv_datagram with MSG_PEEK enabled
      it is left on the socket receive queue.  This means that when we detect
      a checksum error we have to be careful when trying to free the packet
      as someone could have dequeued it in the time being.
      
      Currently this delicate logic is duplicated three times between UDPv4,
      UDPv6 and RAWv6.  This patch moves them into a one place and simplifies
      the code somewhat.
      
      This is based on a suggestion by Eric Dumazet.
      Signed-off-by: NHerbert Xu <herbert@gondor.apana.org.au>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      3305b80c
    • A
      [ICSK]: Rename struct tcp_func to struct inet_connection_sock_af_ops · 8292a17a
      Arnaldo Carvalho de Melo 提交于
      And move it to struct inet_connection_sock. DCCP will use it in the
      upcoming changesets.
      Signed-off-by: NArnaldo Carvalho de Melo <acme@mandriva.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      8292a17a
    • A
      [IPV6]: Introduce inet6_rsk() · ca304b61
      Arnaldo Carvalho de Melo 提交于
      And inet6_rsk_offset in inet_request_sock, for the same reasons as
      inet_sock's pinfo6 member.
      Signed-off-by: NArnaldo Carvalho de Melo <acme@mandriva.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      ca304b61
    • H
      [IPV4]: Safer reassembly · 89cee8b1
      Herbert Xu 提交于
      Another spin of Herbert Xu's "safer ip reassembly" patch
      for 2.6.16.
      
      (The original patch is here:
      http://marc.theaimsgroup.com/?l=linux-netdev&m=112281936522415&w=2
      and my only contribution is to have tested it.)
      
      This patch (optionally) does additional checks before accepting IP
      fragments, which can greatly reduce the possibility of reassembling
      fragments which originated from different IP datagrams.
      Signed-off-by: NHerbert Xu <herbert@gondor.apana.org.au>
      Signed-off-by: NArthur Kepner <akepner@sgi.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      89cee8b1
    • T
      [LSM-IPSec]: Security association restriction. · df71837d
      Trent Jaeger 提交于
      This patch series implements per packet access control via the
      extension of the Linux Security Modules (LSM) interface by hooks in
      the XFRM and pfkey subsystems that leverage IPSec security
      associations to label packets.  Extensions to the SELinux LSM are
      included that leverage the patch for this purpose.
      
      This patch implements the changes necessary to the XFRM subsystem,
      pfkey interface, ipv4/ipv6, and xfrm_user interface to restrict a
      socket to use only authorized security associations (or no security
      association) to send/receive network packets.
      
      Patch purpose:
      
      The patch is designed to enable access control per packets based on
      the strongly authenticated IPSec security association.  Such access
      controls augment the existing ones based on network interface and IP
      address.  The former are very coarse-grained, and the latter can be
      spoofed.  By using IPSec, the system can control access to remote
      hosts based on cryptographic keys generated using the IPSec mechanism.
      This enables access control on a per-machine basis or per-application
      if the remote machine is running the same mechanism and trusted to
      enforce the access control policy.
      
      Patch design approach:
      
      The overall approach is that policy (xfrm_policy) entries set by
      user-level programs (e.g., setkey for ipsec-tools) are extended with a
      security context that is used at policy selection time in the XFRM
      subsystem to restrict the sockets that can send/receive packets via
      security associations (xfrm_states) that are built from those
      policies.
      
      A presentation available at
      www.selinux-symposium.org/2005/presentations/session2/2-3-jaeger.pdf
      from the SELinux symposium describes the overall approach.
      
      Patch implementation details:
      
      On output, the policy retrieved (via xfrm_policy_lookup or
      xfrm_sk_policy_lookup) must be authorized for the security context of
      the socket and the same security context is required for resultant
      security association (retrieved or negotiated via racoon in
      ipsec-tools).  This is enforced in xfrm_state_find.
      
      On input, the policy retrieved must also be authorized for the socket
      (at __xfrm_policy_check), and the security context of the policy must
      also match the security association being used.
      
      The patch has virtually no impact on packets that do not use IPSec.
      The existing Netfilter (outgoing) and LSM rcv_skb hooks are used as
      before.
      
      Also, if IPSec is used without security contexts, the impact is
      minimal.  The LSM must allow such policies to be selected for the
      combination of socket and remote machine, but subsequent IPSec
      processing proceeds as in the original case.
      
      Testing:
      
      The pfkey interface is tested using the ipsec-tools.  ipsec-tools have
      been modified (a separate ipsec-tools patch is available for version
      0.5) that supports assignment of xfrm_policy entries and security
      associations with security contexts via setkey and the negotiation
      using the security contexts via racoon.
      
      The xfrm_user interface is tested via ad hoc programs that set
      security contexts.  These programs are also available from me, and
      contain programs for setting, getting, and deleting policy for testing
      this interface.  Testing of sa functions was done by tracing kernel
      behavior.
      Signed-off-by: NTrent Jaeger <tjaeger@cse.psu.edu>
      Signed-off-by: NHerbert Xu <herbert@gondor.apana.org.au>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      df71837d
  2. 25 12月, 2005 1 次提交
  3. 23 12月, 2005 1 次提交
    • N
      [PATCH] fix race with preempt_enable() · d6f02913
      Nicolas Pitre 提交于
      Currently a simple
      
      	void foo(void) { preempt_enable(); }
      
      produces the following code on ARM:
      
      foo:
      	bic	r3, sp, #8128
      	bic	r3, r3, #63
      	ldr	r2, [r3, #4]
      	ldr	r1, [r3, #0]
      	sub	r2, r2, #1
      	tst	r1, #4
      	str	r2, [r3, #4]
      	blne	preempt_schedule
      	mov	pc, lr
      
      The problem is that the TIF_NEED_RESCHED flag is loaded _before_ the
      preemption count is stored back, hence any interrupt coming within that
      3 instruction window causing TIF_NEED_RESCHED to be set won't be
      seen and scheduling won't happen as it should.
      
      Nothing currently prevents gcc from performing that reordering.  There
      is already a barrier() before the decrement of the preemption count, but
      another one is needed between this and the TIF_NEED_RESCHED flag test
      for proper code ordering.
      Signed-off-by: NNicolas Pitre <nico@cam.org>
      Acked-by: NNick Piggin <nickpiggin@yahoo.com.au>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      d6f02913
  4. 22 12月, 2005 1 次提交
    • A
      [PATCH] include/linux/irq.h: #include <linux/smp.h> · 23f9b317
      Adrian Bunk 提交于
      Jan's crosscompile page [1] shows, that one regression in 2.6.15-rc is
      that the v850 defconfig does no longer compile.
      
      The compile error is:
      
      <--  snip  -->
      
      ...
        CC      arch/v850/kernel/setup.o
      In file included from /usr/src/ctest/rc/kernel/arch/v850/kernel/setup.c:17:
      /usr/src/ctest/rc/kernel/include/linux/irq.h:13:43: asm/smp.h: No such file or directory
      make[2]: *** [arch/v850/kernel/setup.o] Error 1
      
      <--  snip  -->
      
      The #include <asm/smp.h> in irq.h was intruduced in 2.6.15-rc.
      
      Since include/linux/irq.h needs code from asm/smp.h only in the
      CONFIG_SMP=y case and linux/smp.h #include's asm/smp.h only in the
      CONFIG_SMP=y case, I'm suggesting this patch to #include <linux/smp.h>
      in irq.h.
      
      I've tested the compilation with both CONFIG_SMP=y and CONFIG_SMP=n
      on i386.
      Signed-off-by: NAdrian Bunk <bunk@stusta.de>
      Acked-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      23f9b317
  5. 21 12月, 2005 2 次提交
  6. 20 12月, 2005 2 次提交
  7. 19 12月, 2005 2 次提交
  8. 17 12月, 2005 2 次提交
  9. 15 12月, 2005 4 次提交
  10. 13 12月, 2005 15 次提交
  11. 12 12月, 2005 1 次提交
  12. 06 12月, 2005 1 次提交
  13. 02 12月, 2005 1 次提交