1. 20 Jun, 2007 2 commits
    • Stephen Hemminger's avatar
      fix build warnings · 6560dbb8
      Stephen Hemminger authored
      Fix problems from recent if.h related changes.
      Signed-off-by: default avatarStephen Hemminger <shemminger@linux-foundation.org>
      6560dbb8
    • Patrick McHardy's avatar
      [Fwd: Re: more iproute2 issues (not critical)] · c6ab5b82
      Patrick McHardy authored
      This one also makes sense for the release I guess.
      
      -------- Original Message --------
      Subject: 	Re: more iproute2 issues (not critical)
      Date: 	Sat, 31 Mar 2007 16:16:56 +0200
      From: 	Patrick McHardy <kaber@trash.net>
      To: 	Denys <denys@visp.net.lb>
      CC: 	Stephen Hemminger <shemminger@linux-foundation.org>,
      netdev@vger.kernel.org
      References: 	<20070321175951.M73913@visp.net.lb>
      <46026717.9060909@trash.net> <20070322124533.M79867@visp.net.lb>
      <46027FF2.6020001@trash.net> <20070322101224.3e6bb899@freekitty>
      <20070331021401.M17326@visp.net.lb> <20070331023011.M8101@visp.net.lb>
      
      Denys wrote:
      > Ooops, sorry, it seems my fault, no library exist on this system.
      > But i guess it must not coredump in this case? Is it possible to check if
      > library not exist and just print some nice message?
      > It is trivial i guess.
      
      The problem is that lib_dir is NULL when calling get_target_names.
      This patch fixes it.
      
      [IPROUTE]: m_ipt: fix crash when dumping rules
      
      lib_dir is NULL when calling get_target_name, causing a NULL pointer
      dereference in the strlen call.
      Signed-off-by: default avatarPatrick McHardy <kaber@trash.net>
      c6ab5b82
  2. 19 Jun, 2007 9 commits
  3. 11 May, 2007 1 commit
  4. 16 Mar, 2007 1 commit
  5. 14 Mar, 2007 1 commit
    • Stephen Hemminger's avatar
      Revert "Increase internal clock resolution to nsec" · 89151447
      Stephen Hemminger authored
      This reverts fd784cca commit.
      
      Thanks Stephen, but actually I think the last patch (increase clock
      resolution) shouldn't go in yet. I'm not done yet looking at all
      the compatibility issues and it does change the range of valid
      values for everything dealing with times. Most places I looked
      at still accept reasonable ranges, but I would feel more comfortable
      to make sure everything is fine first.
      89151447
  6. 13 Mar, 2007 13 commits
  7. 07 Mar, 2007 2 commits
  8. 06 Mar, 2007 3 commits
  9. 20 Feb, 2007 1 commit
  10. 09 Jan, 2007 1 commit
  11. 14 Dec, 2006 6 commits