1. 11 Mar, 2011 1 commit
  2. 04 Jan, 2011 1 commit
    • Francois-Xavier Le Bail's avatar
      net: typos in comments in include/linux/igmp.h · 7b26e5eb
      Francois-Xavier Le Bail authored
      There are typos in comments in include/linux/igmp.h:
      83 #define IGMP_HOST_MEMBERSHIP_QUERY      0x11    /* From RFC1112 */
      84 #define IGMP_HOST_MEMBERSHIP_REPORT     0x12    /* Ditto */
      88 #define IGMPV2_HOST_MEMBERSHIP_REPORT   0x16    /* V2 version of 0x11 */
      89 #define IGMP_HOST_LEAVE_MESSAGE         0x17
      90 #define IGMPV3_HOST_MEMBERSHIP_REPORT   0x22    /* V3 version of 0x11 */
      The line 88 and 90 are about REPORT messages.
      The IGMP_HOST_MEMBERSHIP_REPORT (IGMP V1) value is 0x12.
      So the comment on line 88 must be /* V2 version of 0x12 */,
      and the comment on line 90 must be /* V3 version of 0x12 */.
      Signed-off-by: default avatarFrancois-Xavier Le Bail <fx.lebail@orange.fr>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
  3. 18 Nov, 2010 1 commit
  4. 12 Nov, 2010 1 commit
  5. 02 Feb, 2010 1 commit
  6. 04 Nov, 2009 1 commit
  7. 15 Sep, 2009 1 commit
    • Moni Shoua's avatar
      bonding: remap muticast addresses without using dev_close() and dev_open() · 75c78500
      Moni Shoua authored
      This patch fixes commit e36b9d16. The approach
      there is to call dev_close()/dev_open() whenever the device type is changed in
      order to remap the device IP multicast addresses to HW multicast addresses.
      This approach suffers from 2 drawbacks:
      *. It assumes tha the device is UP when calling dev_close(), or otherwise
         dev_close() has no affect. It is worth to mention that initscripts (Redhat)
         and sysconfig (Suse) doesn't act the same in this matter. 
      *. dev_close() has other side affects, like deleting entries from the routing
         table, which might be unnecessary.
      The fix here is to directly remap the IP multicast addresses to HW multicast
      addresses for a bonding device that changes its type, and nothing else.
      Reported-by: default avatarJason Gunthorpe <jgunthorpe@obsidianresearch.com>
      Signed-off-by: default avatarMoni Shoua <monis@voltaire.com>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
  8. 30 Jan, 2009 1 commit
  9. 14 Oct, 2008 1 commit
  10. 03 Jul, 2008 1 commit
  11. 24 Mar, 2008 1 commit
  12. 26 Apr, 2007 2 commits
  13. 06 Mar, 2007 1 commit
    • Jay Vosburgh's avatar
      bonding: Improve IGMP join processing · a816c7c7
      Jay Vosburgh authored
      	In active-backup mode, the current bonding code duplicates IGMP
      traffic to all slaves, so that switches are up to date in case of a
      failover from an active to a backup interface.  If bonding then fails
      back to the original active interface, it is likely that the "active
      slave" switch's IGMP forwarding for the port will be out of date until
      some event occurs to refresh the switch (e.g., a membership query).
      	This patch alters the behavior of bonding to no longer flood
      IGMP to all ports, and to issue IGMP JOINs to the newly active port at
      the time of a failover.  This insures that switches are kept up to date
      for all cases.
      	"GOELLESCH Niels" <niels.goellesch@eurocontrol.int> originally
      reported this problem, and included a patch.  His original patch was
      modified by Jay Vosburgh to additionally remove the existing IGMP flood
      behavior, use RCU, streamline code paths, fix trailing white space, and
      adjust for style.
      Signed-off-by: default avatarJay Vosburgh <fubar@us.ibm.com>
      Signed-off-by: default avatarJeff Garzik <jeff@garzik.org>
  14. 04 Dec, 2006 1 commit
  15. 03 Dec, 2006 1 commit
  16. 22 Nov, 2006 1 commit
  17. 29 Sep, 2006 6 commits
  18. 18 Jun, 2006 1 commit
  19. 29 Aug, 2005 1 commit
  20. 09 Jul, 2005 1 commit
    • David L Stevens's avatar
      [IPV4]: multicast API "join" issues · ca9b907d
      David L Stevens authored
              This patch corrects a few problems with the IP_ADD_MEMBERSHIP
      socket option:
      1) The existing code makes an attempt at reference counting joins when
         using the ip_mreqn/imr_ifindex interface. Joining the same group
         on the same socket is an error, whatever the API. This leads to
         unexpected results when mixing ip_mreqn by index with ip_mreqn by
         address, ip_mreq, or other API's. For example, ip_mreq followed by
         ip_mreqn of the same group will "work" while the same two reversed
         will not.
                 Fixed to always return EADDRINUSE on a duplicate join and
         removed the (now unused) reference count in ip_mc_socklist.
      2) The group-search list in ip_mc_join_group() is comparing a full 
         ip_mreqn structure and all of it must match for it to find the
         group. This doesn't correctly match a group that was joined with
         ip_mreq or ip_mreqn with an address (with or without an index). It
         also doesn't match groups that are joined by different addresses on
         the same interface. All of these are the same multicast group,
         which is identified by group address and interface index.
                 Fixed the check to correctly match groups so we don't get
         duplicate group entries on the ip_mc_socklist.
      3) The old code allocates a multicast address before searching for
         duplicates requiring it to free in various error cases. This
         patch moves the allocate until after the search and
         igmp_max_memberships check, so never a need to allocate, then free
         an entry.
      Signed-off-by: default avatarDavid L Stevens <dlstevens@us.ibm.com>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
  21. 16 Apr, 2005 1 commit
    • Linus Torvalds's avatar
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds authored
      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!