Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Commits on Sep 30, 2005
  1. Linux v2.6.14-rc3

    Linus Torvalds authored
  2. [PATCH] x86_64 early numa init fix

    Ravikiran G Thirumalai authored Linus Torvalds committed
    The tests Alok carried out on Petr's box confirmed that cpu_to_node[BP] is
    not setup early enough by numa_init_array due to the x86_64 changes in
    2.6.14-rc*, and unfortunately set wrongly by the work around code in
    numa_init_array().  cpu_to_node[0] gets set with 1 early and later gets set
    properly to 0 during identify_cpu() when all cpus are brought up, but
    confusing the numa slab in the process.
    
    Here is a quick fix for this.  The right fix obviously is to have
    cpu_to_node[bsp] setup early for numa_init_array().  The following patch
    will fix the problem now, and the code can stay on even when
    cpu_to_node{BP] gets fixed early correctly.
    
    Thanks to Petr for access to his box.
    
    Signed off by: Ravikiran Thirumalai <kiran@scalex86.org>
    Signed-off-by: Alok N Kataria <alokk@calsoftinc.com>
    Signed-off-by: Andrew Morton <akpm@osdl.org>
    Signed-off-by: Linus Torvalds <torvalds@osdl.org>
  3. [PATCH] x86_64: fix the BP node_to_cpumask

    Ravikiran G Thirumalai authored Linus Torvalds committed
    Fix the BP node_to_cpumask.  2.6.14-rc* broke the boot cpu bit as the
    cpu_to_node(0) is now not setup early enough for numa_init_array.
    cpu_to_node[] is setup much later at srat_detect_node on acpi srat based
    em64t machines.  This seems like a problem on amd machines too, Tested on
    em64t though.  /sys/devices/system/node/node0/cpumap shows up sanely after
    this patch.
    
    Signed off by: Ravikiran Thirumalai <kiran@scalex86.org>
    Signed-off-by: Shai Fultheim <shai@scalex86.org>
    Cc: Andi Kleen <ak@muc.de>
    Signed-off-by: Andrew Morton <akpm@osdl.org>
    Signed-off-by: Linus Torvalds <torvalds@osdl.org>
  4. [PATCH] utilization of kprobe_mutex is incorrect on x86_64

    Zhang, Yanmin authored Linus Torvalds committed
    The up()/down() orders are incorrect in arch/x86_64/kprobes.c file.
    kprobe_mutext is used to protect the free kprobe instruction slot list.
    arch_prepare_kprobe applies for a slot from the free list, and
    arch_remove_kprobe returns a slot to the free list.  The incorrect up()/down()
    orders to operate on kprobe_mutex fail to protect the free list.  If 2 threads
    try to get/return kprobe instruction slot at the same time, the free slot list
    might be broken, or a free slot might be applied by 2 threads.
    
    Signed-off-by: Zhang Yanmin <Yanmin.zhang@intel.com>
    Cc: Andi Kleen <ak@muc.de>
    Signed-off-by: Andrew Morton <akpm@osdl.org>
    Signed-off-by: Linus Torvalds <torvalds@osdl.org>
  5. [PATCH] ohci1394: less noise in dmesg

    Jody McIntyre authored Linus Torvalds committed
    less noise in dmesg
    
    Signed-off-by: Ben Collins <bcollins@debian.org>
    Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de>
    Signed-off-by: Jody McIntyre <scjody@steamballoon.com>
    Signed-off-by: Andrew Morton <akpm@osdl.org>
    Signed-off-by: Linus Torvalds <torvalds@osdl.org>
  6. [PATCH] ieee1394: delete legacy module aliases

    Jody McIntyre authored Linus Torvalds committed
    amdtp, dv1394, raw1394, video1394:
    
    Delete legacy module aliases.  The macros did not work and the aliases are not
    needed nowadays.
    
    Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de>
    Signed-off-by: Ben Collins <bcollins@debian.org>
    Signed-off-by: Jody McIntyre <scjody@steamballoon.com>
    Signed-off-by: Andrew Morton <akpm@osdl.org>
    Signed-off-by: Linus Torvalds <torvalds@osdl.org>
  7. [PATCH] eth1394: workaround limitation in rawiso routines

    Jody McIntyre authored Linus Torvalds committed
    Work around limitation in rawiso routines.  Required with 1394b cards on
    architectures where PAGE_SIZE is 4096.  Based on a previous patch by Ben
    Collins.
    
    Signed-off-by: Jody McIntyre <scjody@steamballoon.com>
    Cc: Ben Collins <bcollins@debian.org>
    Signed-off-by: Andrew Morton <akpm@osdl.org>
    Signed-off-by: Linus Torvalds <torvalds@osdl.org>
  8. [PATCH] ieee1394: remove superfluous include in csr1212

    Jody McIntyre authored Linus Torvalds committed
    Remove superfluous include.
    
    Signed-off-by: Jody McIntyre <scjody@steamballoon.com>
    Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de>
    Signed-off-by: Jody McIntyre <scjody@steamballoon.com>
    Cc: Ben Collins <bcollins@debian.org>
    Signed-off-by: Andrew Morton <akpm@osdl.org>
    Signed-off-by: Linus Torvalds <torvalds@osdl.org>
  9. [PATCH] ieee1394: trivial edits of a few comments

    Jody McIntyre authored Linus Torvalds committed
    trivial edits of a few comments
    
    Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de>
    Signed-off-by: Ben Collins <bcollins@debian.org>
    Signed-off-by: Jody McIntyre <scjody@steamballoon.com>
    Signed-off-by: Andrew Morton <akpm@osdl.org>
    Signed-off-by: Linus Torvalds <torvalds@osdl.org>
  10. [PATCH] ieee1394: use time_before()

    Jody McIntyre authored Linus Torvalds committed
    Use of time_before() macro, defined at linux/jiffies.h, which deal with
    wrapping correctly and are nicer to read.
    
    Signed-off-by: Marcelo Feitoza Parisi <marcelo@feitoza.com.br>
    Signed-off-by: Domen Puncer <domen@coderock.org>
    Signed-off-by: Ben Collins <bcollins@debian.org>
    Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de>
    Signed-off-by: Jody McIntyre <scjody@steamballoon.com>
    Signed-off-by: Andrew Morton <akpm@osdl.org>
    Signed-off-by: Linus Torvalds <torvalds@osdl.org>
  11. [PATCH] ieee1394: fix for debug output

    Jody McIntyre authored Linus Torvalds committed
    Fix debug code so it prints the correct speed (was defaulting to 100, so
    anything > 400 showed only 100).
    
    Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de>
    Signed-off-by: Ben Collins <bcollins@debian.org>
    Signed-off-by: Jody McIntyre <scjody@steamballoon.com>
    Signed-off-by: Andrew Morton <akpm@osdl.org>
    Signed-off-by: Linus Torvalds <torvalds@osdl.org>
  12. [PATCH] ieee1394: skip unnecessary pause when scanning config ROMs

    Jody McIntyre authored Linus Torvalds committed
    Skip a superfluous pause that occured when the config ROM of a node was
    scanned unsuccessfully.  This also occurs if a node without link wrongly
    enables its "link active" self ID flag.  A GWCTech 6-port hub does this.
    
    Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de>
    Signed-off-by: Jody McIntyre <scjody@steamballoon.com>
    Cc: Ben Collins <bcollins@debian.org>
    Signed-off-by: Andrew Morton <akpm@osdl.org>
    Signed-off-by: Linus Torvalds <torvalds@osdl.org>
  13. [PATCH] ieee1394: reorder activities after bus reset (fixes device de…

    Jody McIntyre authored Linus Torvalds committed
    …tection)
    
    Units were not detected if the local IRM performed a bus reset.  ("The root
    node is not cycle master capable; selecting a new root node and resetting...",
    often seen with iPods and other SBP-2 devices).  Rearrange the order of IRM
    duties and node scanning.  TODO: Audit the ROM caching and parsing code for
    underlying issues.
    
    Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de>
    Signed-off-by: Jody McIntyre <scjody@steamballoon.com>
    Cc: Ben Collins <bcollins@debian.org>
    Signed-off-by: Andrew Morton <akpm@osdl.org>
    Signed-off-by: Linus Torvalds <torvalds@osdl.org>
  14. [PATCH] sbp2: default to serialize_io=1

    Jody McIntyre authored Linus Torvalds committed
    Set serialize_io=1 by default.  This is safer and required by seemingly more
    and more hardware.  It causes little or no performance loss for S400 devices.
    Performance of S800 1394b devices may drop by 25...30%.  Therefore make the
    parameter's description and dmesg message clearer about performance impact.
    
    Update description of the max_speed parameter too.  IEEE1394_SPEED_MAX is
    currently S800.
    
    Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de>
    Signed-off-by: Jody McIntyre <scjody@steamballoon.com>
    Cc: Ben Collins <bcollins@debian.org>
    Signed-off-by: Andrew Morton <akpm@osdl.org>
    Signed-off-by: Linus Torvalds <torvalds@osdl.org>
  15. [PATCH] sbp2: fix deadlocks and delays on device removal/rmmod

    Jody McIntyre authored Linus Torvalds committed
    Fixes for deadlocks of the ieee1394 and scsi subsystems and long delays in
    futile error recovery attempts when SBP-2 devices are removed or drivers are
    unloaded.
    
     - Complete commands quickly with DID_NO_CONNECT if the 1394 node is gone or if
       the 1394 low-level driver was unloaded.
     - Skip unnecessary work in the eh_abort_handler and eh_device_reset_handler if
       the node or 1394 low-level driver is gone.
     - Let scsi's high-level shut down gracefully when sbp2 is being unloaded or
       detached from the 1394 unit. A call to scsi_remove_device is added for this
       purpose, which requires us to store a scsi_device pointer.
     - scsi_device pointer is obtained from slave_alloc hook and cleared by
       slave_destroy. This avoids usage of the pointer after the scsi device was
       deleted e.g. by the user via scsi_mod's sysfs interface.
    
    Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de>
    Signed-off-by: Jody McIntyre <scjody@steamballoon.com>
    Cc: Ben Collins <bcollins@debian.org>
    Signed-off-by: Andrew Morton <akpm@osdl.org>
    Signed-off-by: Linus Torvalds <torvalds@osdl.org>
  16. [PATCH] MAINTAINERS: sbp2 driver is not orphaned.

    Jody McIntyre authored Linus Torvalds committed
    Cc: Ben Collins <bcollins@debian.org>
    Signed-off-by: Andrew Morton <akpm@osdl.org>
    Signed-off-by: Linus Torvalds <torvalds@osdl.org>
  17. [PATCH] ioc4_serial: Remove bogus error message

    Brent Casavant authored Linus Torvalds committed
    This change removes a bogus error message from the IOC4 serial driver
    interrupt handler.
    
    This error message is bogus for two reasons.  First, it can never occur
    given that current code takes care to initialize IOC4 in such a way that
    these "unknown" interrupts could never occur.  Second, this code fails to
    take into account that other drivers can share the IOC4 interrupt mechanism
    through SA_SHIRQ, and thus this driver is not in-fact "all-knowing".
    
    Finally, this error message triggers every time some "unknown" interrupt
    occurs -- it's not rate limited or repetition limited in any way, thereby
    effectively denying use of the console device.  Given its bogosity in the
    first place, it's best to just get rid of it entirely.
    
    Acked-by: Pat Gefre <pfg@sgi.com>
    Signed-off-by: Brent Casavant <bcasavan@sgi.com>
    Signed-off-by: Andrew Morton <akpm@osdl.org>
    Signed-off-by: Linus Torvalds <torvalds@osdl.org>
  18. [PATCH] fuse: check O_DIRECT

    Miklos Szeredi authored Linus Torvalds committed
    Check O_DIRECT and return -EINVAL error in open.  dentry_open() also checks
    this but only after the open method is called.  This patch optimizes away
    the unnecessary upcalls in this case.
    
    It could be a correctness issue too: if filesystem has open() with side
    effect, then it should fail before doing the open, not after.
    
    Signed-off-by: Miklos Szeredi <miklos@szeredi.hu>
    Signed-off-by: Andrew Morton <akpm@osdl.org>
    Signed-off-by: Linus Torvalds <torvalds@osdl.org>
  19. [PATCH] uml: remove empty hostfs_truncate method

    Paolo 'Blaisorblade' Giarrusso authored Linus Torvalds committed
    Calling truncate() on hostfs spits a kernel warning "Something isn't
    implemented here", but it still works fine.
    
    Indeed, hostfs i_op->truncate doesn't do anything.  But hostfs_setattr() ->
    set_attr() correctly detects ATTR_SIZE and calls truncate() on the host.  So
    we should be safe (using ftruncate() may be better, in case the file is
    unlinked on the host, but we aren't sure to have the file open for writing,
    and reopening it would cause the same races; plus nobody should expect UML to
    be so careful).
    
    So, the warning is wrong, because the current implementation is working.  Al,
    am I correct, and can the warning be therefore dropped?
    
    CC: Al Viro <viro@zeniv.linux.org.uk>
    Signed-off-by: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
    Signed-off-by: Andrew Morton <akpm@osdl.org>
    Signed-off-by: Linus Torvalds <torvalds@osdl.org>
  20. [PATCH] uml: revert "run mconsole "sysrq" in process context"

    Paolo 'Blaisorblade' Giarrusso authored Linus Torvalds committed
    Revert commit 12ebcd7, i.e.  [PATCH] uml: run
    mconsole "sysrq" in process context on request from Jeff Dike.
    
    a) sysrq may be run when the scheduler is non-functioning
    
    b) the warning I wanted to fix actually came from the fault handler run in
       atomic context.  But I fixed that not to take the semaphore in a separate
       patch.
    
    c) the fault handler is run because of a fault, and that fault was
       unaffected by this patch.
    
    Signed-off-by: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
    Signed-off-by: Andrew Morton <akpm@osdl.org>
    Signed-off-by: Linus Torvalds <torvalds@osdl.org>
  21. [PATCH] uml: clear SKAS0/3 flags when running in TT mode

    Paolo 'Blaisorblade' Giarrusso authored Linus Torvalds committed
    SEGV_MAYBE_FIXABLE tests ptrace_faultinfo, and depends on it being 1 only in
    SKAS3 mode, while currently when running with mode=tt it will be 1 anyway.
    Fix this, and do the same for proc_mm.
    
    Signed-off-by: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
    Signed-off-by: Andrew Morton <akpm@osdl.org>
    Signed-off-by: Linus Torvalds <torvalds@osdl.org>
  22. [PATCH] uml: fix page faults in SKAS3 mode.

    Paolo 'Blaisorblade' Giarrusso authored Linus Torvalds committed
    I hadn't been running a SKAS3 host when testing the "uml: fix hang in TT mode
    on fault" patch (commit 546fe1c), and I
    didn't think enough to the missing trap_no in SKAS3 mode.
    
    In fact, the resulting kernel doesn't work at all in SKAS3 mode.
    
    Signed-off-by: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
    Signed-off-by: Andrew Morton <akpm@osdl.org>
    Signed-off-by: Linus Torvalds <torvalds@osdl.org>
  23. @mkrufky

    [PATCH] v4l: DViCO FusionHDTV5 Lite GPIO Fix

    mkrufky authored Linus Torvalds committed
    GPIO fix for the composite and tv mute states of bt8xx card #135: DViCO
    FusionHDTV5 Lite.  Without this patch, selecting one of these states could
    produce unexpected behavior.
    
    Signed-off-by: Michael Krufky <mkrufky@linuxtv.org>
    Signed-off-by: Mauro Carvalho Chehab <mchehab@brturbo.com.br>
    Signed-off-by: Andrew Morton <akpm@osdl.org>
    Signed-off-by: Linus Torvalds <torvalds@osdl.org>
  24. [PATCH] x86: hw_irq.h warning fix

    Andrew Morton authored Linus Torvalds committed
    include/asm/hw_irq.h:70: warning: `struct hw_interrupt_type' declared inside parameter list
    include/asm/hw_irq.h:70: warning: its scope is only this definition or declaration, which is probably not what you want
    
    Signed-off-by: Andrew Morton <akpm@osdl.org>
    Signed-off-by: Linus Torvalds <torvalds@osdl.org>
  25. [PATCH] aio: avoid extra aio_{read,write} call when ki_left == 0

    Zach Brown authored Linus Torvalds committed
    Recently aio_p{read,write} changed to perform retries internally rather
    than returning -EIOCBRETRY.  This inadvertantly resulted in always calling
    aio_{read,write} with ki_left at 0 which would in turn immediately return
    0.  Harmless, but we can avoid this call by checking in the caller.
    
    Signed-off-by: Zach Brown <zach.brown@oracle.com>
    Signed-off-by: Benjamin LaHaise <bcrl@linux.intel.com>
    Signed-off-by: Andrew Morton <akpm@osdl.org>
    Signed-off-by: Linus Torvalds <torvalds@osdl.org>
  26. [PATCH] aio: remove unlocked task_list test and resulting race

    Zach Brown authored Linus Torvalds committed
    Only one of the run or kick path is supposed to put an iocb on the run
    list.  If both of them do it than one of them can end up referencing a
    freed iocb.  The kick path could delete the task_list item from the wait
    queue before getting the ctx_lock and putting the iocb on the run list.
    The run path was testing the task_list item outside the lock so that it
    could catch ki_retry methods that return -EIOCBRETRY *without* putting the
    iocb on a wait queue and promising to call kick_iocb.  This unlocked check
    could then race with the kick path to cause both to try and put the iocb on
    the run list.
    
    The patch stops the run path from testing task_list by requring that any
    ki_retry that returns -EIOCBRETRY *must* guarantee that kick_iocb() will be
    called in the future.  aio_p{read,write}, the only in-tree -EIOCBRETRY
    users, are updated.
    
    Signed-off-by: Zach Brown <zach.brown@oracle.com>
    Signed-off-by: Benjamin LaHaise <bcrl@linux.intel.com>
    Signed-off-by: Andrew Morton <akpm@osdl.org>
    Signed-off-by: Linus Torvalds <torvalds@osdl.org>
  27. [PATCH] aio: lock around kiocbTryKick()

    Zach Brown authored Linus Torvalds committed
    Only one of the run or kick path is supposed to put an iocb on the run
    list.  If both of them do it than one of them can end up referencing a
    freed iocb.  The kick patch could set the Kicked bit before acquiring the
    ctx_lock and putting the iocb on the run list.  The run path, while holding
    the ctx_lock, could see this partial kick and mistake it for a kick that
    was deferred while it was doing work with the run_list NULLed out.  It
    would then race with the kick thread to add the iocb to the run list.
    
    This patch moves the kick setting under the ctx_lock so that only one of
    the kick or run path queues the iocb on the run list, as intended.
    
    Signed-off-by: Zach Brown <zach.brown@oracle.com>
    Signed-off-by: Benjamin LaHaise <bcrl@linux.intel.com>
    Signed-off-by: Andrew Morton <akpm@osdl.org>
    Signed-off-by: Linus Torvalds <torvalds@osdl.org>
  28. Revert "x86-64: Reverse order of bootmem lists"

    Linus Torvalds authored
    As requested by Thomas Gleixner <tglx@linutronix.de>:
    
      "5d3d0f7704ed0bc7eaca0501eeae3e5da1ea6c87 breaks a couple of ARM
       boards, which depend on the historical bootmem allocation order.
       There is a cleaner solution around to remove the pgdat list
       completely, but this is a topic for post 2.6.14
    
       Andi signalled ACK already."
    
    Signed-off-by: Linus Torvalds <torvalds@osdl.org>
  29. [PATCH] SELinux - fix SCTP socket bug and general IP protocol handling

    James Morris authored Linus Torvalds committed
    The following patch updates the way SELinux classifies and handles IP
    based protocols.
    
    Currently, IP sockets are classified by SELinux as being either TCP, UDP
    or 'Raw', the latter being a default for IP socket that is not TCP or UDP.
    
    The classification code is out of date and uses only the socket type
    parameter to socket(2) to determine the class of IP socket.  So, any
    socket created with SOCK_STREAM will be classified by SELinux as TCP, and
    SOCK_DGRAM as UDP.  Also, other socket types such as SOCK_SEQPACKET and
    SOCK_DCCP are currently ignored by SELinux, which classifies them as
    generic sockets, which means they don't even get basic IP level checking.
    
    This patch changes the SELinux IP socket classification logic, so that
    only an IPPROTO_IP protocol value passed to socket(2) classify the socket
    as TCP or UDP.  The patch also drops the check for SOCK_RAW and converts
    it into a default, so that socket types like SOCK_DCCP and SOCK_SEQPACKET
    are classified as SECCLASS_RAWIP_SOCKET (instead of generic sockets).
    
    Note that protocol-specific support for SCTP, DCCP etc. is not addressed
    here, we're just getting these protocols checked at the IP layer.
    
    This fixes a reported problem where SCTP sockets were being recognized as
    generic SELinux sockets yet still being passed in one case to an IP level
    check, which then fails for generic sockets.
    
    It will also fix bugs where any SOCK_STREAM socket is classified as TCP or
    any SOCK_DGRAM socket is classified as UDP.
    
    This patch also unifies the way IP sockets classes are determined in
    selinux_socket_bind(), so we use the already calculated value instead of
    trying to recalculate it.
    
    Signed-off-by: James Morris <jmorris@namei.org>
    Signed-off-by: Stephen Smalley <sds@tycho.nsa.gov>
    Signed-off-by: Linus Torvalds <torvalds@osdl.org>
  30. [PATCH] i386: include linux/irq.h rather than asm/hw_irq.h

    Nick Piggin authored Linus Torvalds committed
    I need the following patch to compile -git8 here, otherwise these
    files fail to compile (asm/hw_irq.h needs definitions from
    linux/irq.h and that file provides the required include ordering).
    
    I did not do a full audit, though there looks to be many other
    places that should get the same treatment, if this is  the right
    way to do it.
    
    Signed-off-by: Linus Torvalds <torvalds@osdl.org>
  31. @dr-itz

    [PATCH] usb/core/hcd-pci.c: don't free_irq() on suspend

    dr-itz authored Linus Torvalds committed
    the free_irq() in USB suspend breaks resume on some setups where USB
    (ohci/ehci) shares the interrupt with an other device.
    
    Signed-off-by: Daniel Ritz <daniel.ritz@gmx.ch>
    Signed-off-by: Linus Torvalds <torvalds@osdl.org>
  32. [PATCH] x86_64: Add missing () around arguments of pte_index macro

    Kirill Korotaev authored Linus Torvalds committed
    x86-64: Add missing () around arguments of pte_index macro
    
    Signed-Off-By: Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>
    Signed-Off-By: Kirill Korotaev <dev@sw.ru>
    Signed-off-by: Linus Torvalds <torvalds@osdl.org>
  33. [PATCH] useless includes of linux/irq.h (arch/ppc)

    Al Viro authored Linus Torvalds committed
    Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
    Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Something went wrong with that request. Please try again.