1. 26 Oct, 2003 12 commits
    • Hideaki Yoshifuji's avatar
      [IPV6]: Typo in address comparison. · 63d6889d
      Hideaki Yoshifuji authored
      63d6889d
    • Andi Kleen's avatar
      [NET]: Fix oops in ethertap_rx(). · 1894c622
      Andi Kleen authored
      1894c622
    • John Levon's avatar
      [NETFILTER]: Fix modular iptables build. · cc2c9aa0
      John Levon authored
      cc2c9aa0
    • David S. Miller's avatar
      Merge nuts.ninka.net:/disk1/davem/BK/network-2.5 · d6611edf
      David S. Miller authored
      into nuts.ninka.net:/disk1/davem/BK/net-2.5
      d6611edf
    • Linus Torvalds's avatar
      Add a sticky "PF_DEAD" task flag to keep track of dead processes. · edf12049
      Linus Torvalds authored
      Use this to simplify 'finish_task_switch', but perhaps more
      importantly we can use this to track down why some processes
      seem to sometimes not die properly even after having been
      marked as ZOMBIE. The "task->state" flags are too fluid to 
      allow that well.
      edf12049
    • Randolph Chung's avatar
      [PATCH] fix __div64_32 to do division properly · c2988baf
      Randolph Chung authored
      This fixes the generic __div64_32() to correctly handle divisions by
      large 32-bit values (as used by nanosleep() and friends, for example).
      
      It's a simple bit-at-a-time implementation with a reduction of the high
      32-bits handled manually.  Architectures that can do 64/32-bit divisions
      in hardware should implement their own more efficient versions.
      c2988baf
    • Yoshinori Sato's avatar
      [PATCH] fix h8/300 support · d33648ef
      Yoshinori Sato authored
       - add 'sched_clock'
       - delete smplock.h
      d33648ef
    • Andi Kleen's avatar
      [PATCH] Essential x86-64 updates · 7c382efa
      Andi Kleen authored
      The most important part is that it makes x86-64 compile again.
      Without that 2.6 users won't be very happy.
      
      It also works around a bug that allowed every user program to reboot the
      system on B stepping K8.
      
      Also update to match some recent i386 fixes.
      
      Full ChangeLog:
       - Add acpi_pic_set_level_irq to make ACPI compile again
       - Work around compat mode K8 bug in IRET exception handling
       - Increase exception stack. The old 1k stack was too easy
         to overflow (from Jim Paradis, changed by me)
       - Replace safe_smp_processor_id with cpuid (needed for above)
       - When there is only one node always enable fake_node mode
       - Merge with i386 (NTP gettimeofday monoticity fix, irq nr_vectors change)
       - Fix compile problem for UP kernels in time/cpufreq
       - Set all nodes online at bootup
       - Define node_to_cpumask correctly
      7c382efa
    • Stelian Pop's avatar
      [PATCH] meye: documentation · 69c1d1bf
      Stelian Pop authored
      This documents the existence of a forth 'motioneye' camera plugged into
      the USB bus, of course unsupported by the meye driver.
      69c1d1bf
    • Stelian Pop's avatar
      [PATCH] sonypi: fix Zoom/Thumbphrase button events · 33127943
      Stelian Pop authored
      This corrects the Zoom and Thumbphrase button events.
      33127943
    • Andries E. Brouwer's avatar
      [PATCH] Relax FATFS validity tests · 1f690869
      Andries E. Brouwer authored
      The first FAT entry should have the media byte (0xf0,0xf8,...,0xff)
      extended with all 1 bits in the first FAT entry.
      
      Checking this is a good idea, it prevents us from mounting garbage
      as FAT - there is no good magic for FAT.
      
      Unfortunately, Windows does not enforce this, and 2.4 doesn't either.
      It turns out that there are filesystems around (two reports so far) that
      have a zero first FAT entry, and work under Windows and 2.4 but fail to
      mount under 2.6.
      
      So, this weakens the test.
      1f690869
    • Andries E. Brouwer's avatar
      [PATCH] atkbd: 0xfa is ACK · d6e0320f
      Andries E. Brouwer authored
      The 0xfa code can be a key scancode or it can be a protocol scancode.
      
      Only few keyboards use it as a key scancode, and if we always interpret
      it as a protocol scancode then these rare keyboards will have a dead
      key.  If we interpret it as a key scancode then we have a dead keyboard
      in case it was protocol.
      
      Clearly it is safer to prefer to interpret it as a protocol scancode.
      
      This moves the test for ACK and NAK up, so that they are always seen as
      protocol.
      
      This is just a minimal patch.  What I did in 1.1.54 was to keep track of
      commands sent with a flag reply_expected, so that 0xfa could be taken as
      ACK when a reply is expected and as key scancode otherwise.  That is the
      better solution, but requires larger surgery.
      d6e0320f
  2. 25 Oct, 2003 2 commits
  3. 24 Oct, 2003 6 commits
  4. 25 Oct, 2003 1 commit
  5. 24 Oct, 2003 5 commits
    • Knut Petersen's avatar
      [PATCH] setkeycode ioctl fix · 99438d1e
      Knut Petersen authored
      This is a bugfix for setkeycode() in /drivers/char/keyboard.c.
      
      If we change a keycode the corresponding bit should be cleared if and
      only if this keycode is not defined any longer.  I believe that this
      also was intended with the original code, but the implementation is
      faulty.
      
      First off all the first three changed lines are obviously erroneus:
      oldkey == truekey is false or true, you do not need to inclose this in a
      for().  I believe the author intended INPUT_KEYCODE(dev,i) == oldkey.
      But fixing this alone is not enough.
      
      If somebody wants to interchange the definition of two keys A and B, the
      normal way is to use two setkeycode calls:
      
          setkeycode (scancode A, keycode B);
          setkeycode (scancode B, keycode A);
      
      The old code does a clearbit(oldkey ..) call even in situations where
      two keys have the same definition, and this situation arises commonly in
      the situation mentioned above.
      
      Both errors are fixed with this patch.
      99438d1e
    • Knut Petersen's avatar
      [PATCH] input / keyboard / Scancode Set 3 support broken · f71a8923
      Knut Petersen authored
      If somebody uses keyboard scancode set 3 it is necessary to explicitly
      program the keyboard to send make/break codes for all keys and to set
      autorepeat for all keys.
      
      This is critical for some people.  One example is the LK461/46W series
      of keyboards from Digital Equipment Corporations.  These are VMS
      keyboards that are also usable on a normal PC.
      
      These keyboards support Scancode Set 2, but for some keys this support
      is screwed up -- some function keys (e.g.  F18/F20) report the same
      scancode sequence combined with both alt and shift keys. 
      
      Scancode Set 3 works perfectly if all keys are programmed to give
      make/break codes. 
      
      A lot of keyboards manufactured by Cherry only make/break for some (not all!)
      modifyer keys in scancode set 3 without this fix.
      f71a8923
    • Linus Torvalds's avatar
      Merge bk://kernel.bkbits.net/gregkh/linux/usb-2.6 · d548fa6f
      Linus Torvalds authored
      into home.osdl.org:/home/torvalds/v2.5/linux
      d548fa6f
    • Linus Torvalds's avatar
      Merge bk://kernel.bkbits.net/davem/sparc-2.5 · 7a2dd9ac
      Linus Torvalds authored
      into home.osdl.org:/home/torvalds/v2.5/linux
      7a2dd9ac
    • Linus Torvalds's avatar
      Add a quirk for the Intel ICH-[45] to add special ACPI regions. · b91728bb
      Linus Torvalds authored
      This fixes resource conflicts due to IO decode that doesn't show
      up with a normal PCI probe (we do similar quirks for most other
      chipsets). Without it, the kernel doesn't know about some magic
      IO decodes for the chips.
      b91728bb
  6. 23 Oct, 2003 14 commits
    • Kazunori Miyazawa's avatar
    • Herbert Xu's avatar
      [IPSEC]: Strengthen policy checks. · 8fe7ee2b
      Herbert Xu authored
      8fe7ee2b
    • Hideaki Yoshifuji's avatar
    • Stephen Hemminger's avatar
    • Alexey Kuznetsov's avatar
      [IPV4]: Fix SKB handling in ipmr xmit. · 1e1d7018
      Alexey Kuznetsov authored
      1e1d7018
    • David S. Miller's avatar
      Merge nuts.ninka.net:/disk1/davem/BK/sparcwork-2.5 · c1183b09
      David S. Miller authored
      into nuts.ninka.net:/disk1/davem/BK/sparc-2.5
      c1183b09
    • David S. Miller's avatar
    • David Brownell's avatar
      [PATCH] USB: usb enumeration clears full speed ep0 state · c1ac1e59
      David Brownell authored
      This resolves a bug that was recently reported to me by someone
      enumerating a USB 1.1 modem through a high speed hub.  I'm a bit
      surprised we never saw it before; I think cache/dma timings must
      usually be strongly in our favor.
      
      The problem was that the HC was still using the old ep0 maxpacket
      value, so when it received an 18 byte device descriptor it would
      report a packet overrun and enumeration would fail.  The fix is
      straightforward:  invalidate the HC's old endpoint state when we
      change the full speed maxpacket size.  (And eventually, we can
      remove EHCI and OHCI code coping with usbcore not doing this.)
      c1ac1e59
    • Stéphane Eranian's avatar
      [PATCH] ia64: fix critical perfmon2 bugs · 7502ff99
      Stéphane Eranian authored
      This patch fixes the following issues:
      
      - fix a nasty corner case by which a task could inherit psr.pp/psr.up
        that could be stale by the time it runs. psr.pp/psr.up bits must be
        cleared on fork and inherited on execve(). Test case provided by
        John Levon.
      
      - mask interrupts when locking the pfm stat structure. We don't want
        to take PMU interrupts in the middle of this kind of critical
        section.
      
      - fix a bug in pfm_close() for context which use asynchronous
        notifications.  You cannot call fasync_helper() with interrupts
        disabled because it reenables them. There was no real danger of
        moving the call outside our critical section.
      
      - fix a bug in in pfm_flush_pmds() where you can leave the freeze bit
        set in the pmc saved state.
      
      - updated dump_pmu_state()
      
      - cleanup the BUG_ON() usage
      7502ff99
    • Arun Sharma's avatar
      [PATCH] ia64: fix broken __emul_prefix · fe6f0598
      Arun Sharma authored
      his seems to be broken for ia32 on ia64 and possibly other emulation
      architectures as well. The problem comes from
      fs/namei.c:set_fs_altroot() using path_lookup() instead of a
      path_walk() relative to "/" (which is the case for 2.4).
      fe6f0598
    • Greg Kroah-Hartman's avatar
      Merge kroah.com:/home/greg/linux/BK/bleed-2.5 · f1aa095a
      Greg Kroah-Hartman authored
      into kroah.com:/home/greg/linux/BK/usb-2.6
      f1aa095a
    • David Brownell's avatar
      [PATCH] USB: fix usb-storage self-deadlock · fa04f891
      David Brownell authored
      This fixes a problem that showed in usb-storage (osdl bugme 1310)
      and could have shown in other drivers that used usb_reset_device()
      when they already held dev->serialize:  a self-deadlock with some
      devices.
      
      There are some drivers that should likely change so that they grab
      this lock themselves, since they don't call this during probe()
      when the lock is already held.  The lock protects against config
      changes by other tasks, which is currently quite rate.
      fa04f891
    • Alan Stern's avatar
      [PATCH] USB: fix for earlier unusual_devs.h patch · e4a93f13
      Alan Stern authored
      An earlier patch caused trouble because it effectively removed the
      US_FL_FIX_INQUIRY flag for devices with release number higher than
      0x5009.  This one might cause problems because it explicitly goes
      against the immediately preceding comment in unusual_devs.h.  That
      comment says that these Casio digital cameras claim to use the CBI
      transport when in fact they only use CB.  However, there have been two
      reports in the last few weeks from people getting the "unneeded SubClass
      and Protocol" log messages.  One of them was using a device with release
      number 0x1000, right at the start of the range.  The other had a device
      with release number 0x5010, just beyond the end of the current range.
      
      Maybe Casio is marketing two different devices with different behaviors
      but having the same Vendor, Product, and Release values -- I don't know.
      e4a93f13
    • Carsten Busse's avatar
      [PATCH] USB: one more digicam for unusual_devs.h · f1d81bfe
      Carsten Busse authored
      its for the Jenoptik JD 5200 z3 Digicam, to enable it to work as a simple
      storage device
      
      more or less i took the values for the 0x0d96 vendor in the 2.6.0-test7
      usb-storage and mixed them with my device id, which seems to work quite well
      
      tested with 2.4.22 kernel
      f1d81bfe