1. 13 May, 2006 7 commits
  2. 12 May, 2006 13 commits
  3. 11 May, 2006 1 commit
  4. 10 May, 2006 1 commit
  5. 08 May, 2006 5 commits
  6. 07 May, 2006 1 commit
    • Lennert Buytenhek's avatar
      [MTD] Convert physmap to platform driver · 73566edf
      Lennert Buytenhek authored
      After dwmw2 let me know it ought to be done, I rewrote the physmap map
      driver to be a platform driver.  I know zilch about the driver model,
      so I probably botched it in some way, but I've done some tests on an
      ixp23xx board which uses physmap, and it all seems to work.
      
      In order to not break existing physmap users, I've added some compat
      code that will instantiate a platform device iff CONFIG_MTD_PHYSMAP_LEN
      is defined and != 0.  Also, I've changed the default value for
      CONFIG_MTD_PHYSMAP_LEN to zero, so that people who inadvertently
      compile in physmap (or new, platform-style, users of physmap) don't get
      burned.
      
      This works pretty well -- the new physmap driver is a drop-in replacement
      for the old one, and works on said ixp23xx board without any code changes
      needed.  (This should hold as long as users don't touch 'physmap_map'
      directly.)
      
      Once all physmap users have been converted to instantiate their own
      platform devices, the compat code can go.  (Or we decide that we can
      change all the in-tree users at the same time, and never merge the
      compat code.)
      Signed-off-by: default avatarLennert Buytenhek <buytenh@wantstofly.org>
      Signed-off-by: default avatarDavid Woodhouse <dwmw2@infradead.org>
      73566edf
  7. 05 May, 2006 1 commit
  8. 03 May, 2006 3 commits
  9. 02 May, 2006 8 commits
    • Ayaz Abdulla's avatar
      forcedeth: fix multi irq issues · ebf34c9b
      Ayaz Abdulla authored
      This patch fixes the issues with multiple irqs.
      
      I am resending based on feedback. I decoupled the dma mask for
      consistent memory and fixed leak with multiple irq in error path.
      
      Thanks to Manfred for catching the spin lock problem.
      Signed-Off-By: default avatarAyaz Abdulla <aabdulla@nvidia.com>
      ebf34c9b
    • Craig Brind's avatar
      [PATCH] via-rhine: zero pad short packets on Rhine I ethernet cards · 3e0d167a
      Craig Brind authored
      Fixes Rhine I cards disclosing fragments of previously transmitted frames
      in new transmissions.
      
      Before transmission, any socket buffer (skb) shorter than the ethernet
      minimum length of 60 bytes was zero-padded.  On Rhine I cards the data can
      later be copied into an aligned transmission buffer without copying this
      padding.  This resulted in the transmission of the frame with the extra
      bytes beyond the provided content leaking the previous contents of this
      buffer on to the network.
      
      Now zero-padding is repeated in the local aligned buffer if one is used.
      
      Following a suggestion from the via-rhine maintainer, no attempt is made
      here to avoid the duplicated effort of padding the skb if it is known that
      an aligned buffer will definitely be used.  This is to make the change
      "obviously correct" and allow it to be applied to a stable kernel if
      necessary.  There is no change to the flow of control and the changes are
      only to the Rhine I code path.
      
      The patch has run on an in-service Rhine-I host without incident.  Frames
      shorter than 60 bytes are now correctly zero-padded when captured on a
      separate host.  I see no unusual stats reported by ifconfig, and no unusual
      log messages.
      Signed-off-by: default avatarCraig Brind <craigbrind@gmail.com>
      Signed-off-by: default avatarRoger Luethi <rl@hellgate.ch>
      Cc: Jeff Garzik <jeff@garzik.org>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarJeff Garzik <jeff@garzik.org>
      3e0d167a
    • Olaf Hering's avatar
      [PATCH] mv643xx_eth: provide sysfs class device symlink · b0b8dab2
      Olaf Hering authored
      On Sat, Mar 11, Olaf Hering wrote:
      > Why is the /sys/class/net/eth0/device symlink not created for the
      > mv643xx_eth driver? Does this work for other platform device drivers?
      > Seems to work for the ps2 keyboard at least.
      
      The SET_NETDEV_DEV has to be done before a call to register_netdev.  With
      the new patch below, the device symlink for the platform device was
      created.  Unfortunately, after the 4 ls commands, the network connection
      died.  No idea if the box crashed or if something else broke, lost remote
      access.
      
      Provide sysfs 'device' in /class/net/ethN Also, set module owner field,
      like pcnet32 driver does.
      Signed-off-by: default avatarOlaf Hering <olh@suse.de>
      Acked-by: default avatarDale Farnsworth <dale@farnsworth.org>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarJeff Garzik <jeff@garzik.org>
      b0b8dab2
    • Jens Axboe's avatar
      [PATCH] vmsplice: restrict stealing a little more · 330ab716
      Jens Axboe authored
      Apply the same rules as the anon pipe pages, only allow stealing
      if no one else is using the page.
      Signed-off-by: default avatarJens Axboe <axboe@suse.de>
      330ab716
    • Jens Axboe's avatar
      [PATCH] splice: fix page LRU accounting · a893b99b
      Jens Axboe authored
      Currently we rely on the PIPE_BUF_FLAG_LRU flag being set correctly
      to know whether we need to fiddle with page LRU state after stealing it,
      however for some origins we just don't know if the page is on the LRU
      list or not.
      
      So remove PIPE_BUF_FLAG_LRU and do this check/add manually in pipe_to_file()
      instead.
      Signed-off-by: default avatarJens Axboe <axboe@suse.de>
      a893b99b
    • Jens Axboe's avatar
      [PATCH] vmsplice: fix badly placed end paranthesis · 7591489a
      Jens Axboe authored
      We need to use the minium of {len, PAGE_SIZE-off}, not {len, PAGE_SIZE}-off.
      The latter doesn't make any sense, and could cause us to attempt negative
      length transfers...
      Signed-off-by: default avatarJens Axboe <axboe@suse.de>
      7591489a
    • Linus Torvalds's avatar
      Merge branch 'audit.b10' of git://git.kernel.org/pub/scm/linux/kernel/git/viro/audit-current · 532f57da
      Linus Torvalds authored
      * 'audit.b10' of git://git.kernel.org/pub/scm/linux/kernel/git/viro/audit-current:
        [PATCH] Audit Filter Performance
        [PATCH] Rework of IPC auditing
        [PATCH] More user space subject labels
        [PATCH] Reworked patch for labels on user space messages
        [PATCH] change lspp ipc auditing
        [PATCH] audit inode patch
        [PATCH] support for context based audit filtering, part 2
        [PATCH] support for context based audit filtering
        [PATCH] no need to wank with task_lock() and pinning task down in audit_syscall_exit()
        [PATCH] drop task argument of audit_syscall_{entry,exit}
        [PATCH] drop gfp_mask in audit_log_exit()
        [PATCH] move call of audit_free() into do_exit()
        [PATCH] sockaddr patch
        [PATCH] deal with deadlocks in audit_free()
      532f57da
    • Patrick McHardy's avatar
      [NETFILTER] x_tables: fix compat related crash on non-x86 · 46c5ea3c
      Patrick McHardy authored
      When iptables userspace adds an ipt_standard_target, it calculates the size
      of the entire entry as:
      
      sizeof(struct ipt_entry) + XT_ALIGN(sizeof(struct ipt_standard_target))
      
      ipt_standard_target looks like this:
      
        struct xt_standard_target
        {
              struct xt_entry_target target;
              int verdict;
        };
      
      xt_entry_target contains a pointer, so when compiled for 64 bit the
      structure gets an extra 4 byte of padding at the end. On 32 bit
      architectures where iptables aligns to 8 byte it will also have 4
      byte padding at the end because it is only 36 bytes large.
      
      The compat_ipt_standard_fn in the kernel adjusts the offsets by
      
        sizeof(struct ipt_standard_target) - sizeof(struct compat_ipt_standard_target),
      
      which will always result in 4, even if the structure from userspace
      was already padded to a multiple of 8. On x86 this works out by
      accident because userspace only aligns to 4, on all other
      architectures this is broken and causes incorrect adjustments to
      the size and following offsets.
      
      Thanks to Linus for lots of debugging help and testing.
      Signed-off-by: default avatarPatrick McHardy <kaber@trash.net>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      46c5ea3c