28 Apr, 2008

1 commit


25 Apr, 2008

1 commit


17 Apr, 2008

3 commits


16 Apr, 2008

4 commits

  • This patch ensures that TIPC properly handles incoming messages
    that have incorrect or unexpected formats. Most significantly,
    it now ensures that each sl_buff has at least as much data as
    the message header indicates it should, and that the entire
    message header is stored contiguously; this prevents TIPC from
    accidentally accessing memory that is not part of the sk_buff.

    Signed-off-by: Allan Stephens
    Signed-off-by: David S. Miller

    Allan Stephens
     
  • This patch allows TIPC to process incoming messages that are
    stored in a fragmented sk_buff, by forcing the linearization
    of any such messages it receives.

    Note: This is an interim solution to allow TIPC to operate with
    Ethernet devices that generate non-linear buffers (such as the
    gianfar driver), until such time as the rest of TIPC is enhanced
    to handle sk_buffs with multiple data areas.

    Signed-off-by: Allan Stephens
    Signed-off-by: David S. Miller

    Allan Stephens
     
  • This patch causes TIPC to allocate fast clonable sk_buffs,
    rather than standard ones. This speeds up the cloning
    operation done by the link code each time a message is sent
    off-node.

    Signed-off-by: Allan Stephens
    Signed-off-by: David S. Miller

    Allan Stephens
     
  • This patch eliminates a null pointer check when discarding a
    TIPC message buffer, since kfree_skb() already handles this
    situation.

    Acknowledgements to Florian Westphal (fw@strlen.de> for
    suggesting this enhancement.

    Signed-off-by: Allan Stephens
    Signed-off-by: David S. Miller

    Allan Stephens
     

15 Apr, 2008

7 commits


14 Apr, 2008

2 commits


27 Mar, 2008

1 commit


26 Mar, 2008

2 commits


07 Mar, 2008

7 commits


04 Mar, 2008

1 commit


25 Feb, 2008

1 commit

  • net/tipc/cluster.c:145:2: warning: Using plain integer as NULL pointer
    net/tipc/link.c:3254:36: warning: Using plain integer as NULL pointer
    net/tipc/ref.c:151:15: warning: Using plain integer as NULL pointer
    net/tipc/zone.c:85:2: warning: Using plain integer as NULL pointer

    Signed-off-by: Harvey Harrison
    Signed-off-by: David S. Miller

    Harvey Harrison
     

08 Feb, 2008

2 commits


29 Jan, 2008

2 commits

  • The file net/tipc/port.c takes a lock using the function tipc_port_lock and
    then releases the lock sometimes using tipc_port_unlock and sometimes using
    spin_unlock_bh(p_ptr->publ.lock). tipc_port_unlock simply does the
    spin_unlock_bh, but it seems cleaner to use it everywhere.

    The problem was fixed using the following semantic patch.
    (http://www.emn.fr/x-info/coccinelle/)

    //
    @@
    struct port *p_ptr;
    @@

    p_ptr = tipc_port_lock(...)
    ...
    (
    p_ptr = tipc_port_lock(...);
    |
    ?- spin_unlock_bh(p_ptr->publ.lock);
    + tipc_port_unlock(p_ptr);
    )
    //

    Signed-off-by: Julia Lawall
    Acked-by: Jon Paul Maloy
    Signed-off-by: David S. Miller

    Julia Lawall
     
  • Many-many code in the kernel initialized the timer->function
    and timer->data together with calling init_timer(timer). There
    is already a helper for this. Use it for networking code.

    The patch is HUGE, but makes the code 130 lines shorter
    (98 insertions(+), 228 deletions(-)).

    Signed-off-by: Pavel Emelyanov
    Acked-by: Arnaldo Carvalho de Melo
    Signed-off-by: David S. Miller

    Pavel Emelyanov
     

15 Dec, 2007

1 commit

  • As noted by Kevin, tipc's release() does down_interruptible() and
    ignores the return value. So if signal_pending() we'll end up doing
    up() on a non-downed semaphore. Fix.

    Signed-off-by: Andrew Morton
    Signed-off-by: David S. Miller

    Andrew Morton
     

01 Nov, 2007

1 commit

  • Finally, the zero_it argument can be completely removed from
    the callers and from the function prototype.

    Besides, fix the checkpatch.pl warnings about using the
    assignments inside if-s.

    This patch is rather big, and it is a part of the previous one.
    I splitted it wishing to make the patches more readable. Hope
    this particular split helped.

    Signed-off-by: Pavel Emelyanov
    Signed-off-by: David S. Miller

    Pavel Emelyanov
     

11 Oct, 2007

4 commits

  • Add inline for common usage of hardware header creation, and
    fix bug in IPV6 mcast where the assumption about negative return is
    an errno. Negative return from hard_header means not enough space
    was available,(ie -N bytes).

    Signed-off-by: Stephen Hemminger
    Signed-off-by: David S. Miller

    Stephen Hemminger
     
  • This is nicer than the MAC_FMT stuff.

    Signed-off-by: Joe Perches
    Signed-off-by: David S. Miller

    Joe Perches
     
  • This patch makes most of the generic device layer network
    namespace safe. This patch makes dev_base_head a
    network namespace variable, and then it picks up
    a few associated variables. The functions:
    dev_getbyhwaddr
    dev_getfirsthwbytype
    dev_get_by_flags
    dev_get_by_name
    __dev_get_by_name
    dev_get_by_index
    __dev_get_by_index
    dev_ioctl
    dev_ethtool
    dev_load
    wireless_process_ioctl

    were modified to take a network namespace argument, and
    deal with it.

    vlan_ioctl_set and brioctl_set were modified so their
    hooks will receive a network namespace argument.

    So basically anthing in the core of the network stack that was
    affected to by the change of dev_base was modified to handle
    multiple network namespaces. The rest of the network stack was
    simply modified to explicitly use &init_net the initial network
    namespace. This can be fixed when those components of the network
    stack are modified to handle multiple network namespaces.

    For now the ifindex generator is left global.

    Fundametally ifindex numbers are per namespace, or else
    we will have corner case problems with migration when
    we get that far.

    At the same time there are assumptions in the network stack
    that the ifindex of a network device won't change. Making
    the ifindex number global seems a good compromise until
    the network stack can cope with ifindex changes when
    you change namespaces, and the like.

    Signed-off-by: Eric W. Biederman
    Signed-off-by: David S. Miller

    Eric W. Biederman
     
  • Every user of the network device notifiers is either a protocol
    stack or a pseudo device. If a protocol stack that does not have
    support for multiple network namespaces receives an event for a
    device that is not in the initial network namespace it quite possibly
    can get confused and do the wrong thing.

    To avoid problems until all of the protocol stacks are converted
    this patch modifies all netdev event handlers to ignore events on
    devices that are not in the initial network namespace.

    As the rest of the code is made network namespace aware these
    checks can be removed.

    Signed-off-by: Eric W. Biederman
    Signed-off-by: David S. Miller

    Eric W. Biederman