1. 23 May, 2006 14 commits
  2. 22 May, 2006 11 commits
  3. 21 May, 2006 15 commits
    • Andrew Morton's avatar
      [PATCH] ad1848 section fix · b307e854
      Andrew Morton authored
      WARNING: sound/oss/ad1848.o - Section mismatch: reference to .init.data:ad1848_isapnp_list from .text between 'ad1848_init_generic' (at offset 0x46f0) and 'kmalloc'
      WARNING: sound/oss/ad1848.o - Section mismatch: reference to .init.data:ad1848_isapnp_list from .text between 'ad1848_init_generic' (at offset 0x46f8) and 'kmalloc'
      WARNING: sound/oss/ad1848.o - Section mismatch: reference to .init.data:ad1848_isapnp_list from .text between 'ad1848_init_generic' (at offset 0x4818) and 'kmalloc'
      
      Also,
      
      sound/oss/ad1848.c: In function `ad1848_init':
      sound/oss/ad1848.c:2029: warning: cast to pointer from integer of different size
      sound/oss/ad1848.c: In function `ad1848_unload':
      sound/oss/ad1848.c:2178: warning: cast to pointer from integer of different size
      sound/oss/ad1848.c: In function `adintr':
      sound/oss/ad1848.c:2207: warning: cast from pointer to integer of different size
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      b307e854
    • Andrew Morton's avatar
      [PATCH] nm256_audio section fix · db314194
      Andrew Morton authored
      WARNING: sound/oss/nm256_audio.o - Section mismatch: reference to .init.text:nm256_peek_for_sig from .text between 'nm256_install' (at offset 0x3ba4) and 'nm256_probe'                                                                         WARNING: sound/oss/nm256_audio.o - Section mismatch: reference to .init.text:nm256_peek_for_sig from .text between 'nm256_install' (at offset 0x3bac) and 'nm256_probe'                                                                         WARNING: sound/oss/nm256_audio.o - Section mismatch: reference to .init.text: from .text between 'nm256_install' (at offset 0x3dcc) and 'nm256_probe'           WARNING: sound/oss/nm256_audio.o - Section mismatch: reference to .init.text: from .text between 'nm256_install' (at offset 0x3dd0) and 'nm256_probe'
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      db314194
    • Andrew Morton's avatar
      [PATCH] es18xx build fix · 1caef6aa
      Andrew Morton authored
      sound/isa/es18xx.c: In function `snd_es18xx_identify':
      sound/isa/es18xx.c:1606: warning: implicit declaration of function `udelay'
      
      Cc: Jaroslav Kysela <perex@suse.cz>
      Cc: Takashi Iwai <tiwai@suse.de>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      1caef6aa
    • Andrew Morton's avatar
      [PATCH] mpu401 section fix · fad43488
      Andrew Morton authored
      WARNING: sound/drivers/mpu401/snd-mpu401.o - Section mismatch: reference to .init.text: from .text between 'snd_mpu401_pnp_probe' (at offset 0x1f7) and 'snd_mpu401_pnp_remove'
      
      Cc: Jaroslav Kysela <perex@suse.cz>
      Cc: Takashi Iwai <tiwai@suse.de>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      fad43488
    • Andrew Morton's avatar
      [PATCH] i810 section fix · 9e8a3d22
      Andrew Morton authored
      WARNING: drivers/video/i810/i810fb.o - Section mismatch: reference to .init.data: from .text between 'i810_fix_offsets' (at offset 0x1b88) and 'i810_alloc_agp_mem'
      WARNING: drivers/video/i810/i810fb.o - Section mismatch: reference to .init.data: from .text between 'i810_fix_offsets' (at offset 0x1b8f) and 'i810_alloc_agp_mem'
      WARNING: drivers/video/i810/i810fb.o - Section mismatch: reference to .init.data: from .text between 'i810_fix_offsets' (at offset 0x1ba3) and 'i810_alloc_agp_mem'
      WARNING: drivers/video/i810/i810fb.o - Section mismatch: reference to .init.data: from .text between 'i810_fix_offsets' (at offset 0x1bb5) and 'i810_alloc_agp_mem'
      WARNING: drivers/video/i810/i810fb.o - Section mismatch: reference to .init.data: from .text between 'i810_fix_offsets' (at offset 0x1bc6) and 'i810_alloc_agp_mem'
      WARNING: drivers/video/i810/i810fb.o - Section mismatch: reference to .init.data: from .text between 'i810_init_defaults' (at offset 0x1dd8) and 'i810_init_device'
      WARNING: drivers/video/i810/i810fb.o - Section mismatch: reference to .init.data: from .text between 'i810_init_defaults' (at offset 0x1dfb) and 'i810_init_device'
      
      Cc: "Antonino A. Daplas" <adaplas@pol.net>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      9e8a3d22
    • Andrew Morton's avatar
      [PATCH] pd6729 section fix · 9781b8b0
      Andrew Morton authored
      WARNING: drivers/pcmcia/pd6729.o - Section mismatch: reference to .init.text: from .text between 'pd6729_pci_probe' (at offset 0x9a8) and 'pd6729_pci_remove'
      
      Cc: Dominik Brodowski <linux@dominikbrodowski.net>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      9781b8b0
    • Bob Picco's avatar
      [PATCH] Align the node_mem_map endpoints to a MAX_ORDER boundary · e984bb43
      Bob Picco authored
      Andy added code to buddy allocator which does not require the zone's
      endpoints to be aligned to MAX_ORDER.  An issue is that the buddy allocator
      requires the node_mem_map's endpoints to be MAX_ORDER aligned.  Otherwise
      __page_find_buddy could compute a buddy not in node_mem_map for partial
      MAX_ORDER regions at zone's endpoints.  page_is_buddy will detect that
      these pages at endpoints are not PG_buddy (they were zeroed out by bootmem
      allocator and not part of zone).  Of course the negative here is we could
      waste a little memory but the positive is eliminating all the old checks
      for zone boundary conditions.
      
      SPARSEMEM won't encounter this issue because of MAX_ORDER size constraint
      when SPARSEMEM is configured.  ia64 VIRTUAL_MEM_MAP doesn't need the logic
      either because the holes and endpoints are handled differently.  This
      leaves checking alloc_remap and other arches which privately allocate for
      node_mem_map.
      Signed-off-by: default avatarBob Picco <bob.picco@hp.com>
      Acked-by: default avatarMel Gorman <mel@csn.ul.ie>
      Cc: Dave Hansen <haveblue@us.ibm.com>
      Cc: Andy Whitcroft <apw@shadowen.org>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      e984bb43
    • Greg Kroah-Hartman's avatar
      [PATCH] kobject: quiet errors in kobject_add · ae57a856
      Greg Kroah-Hartman authored
      People don't like released kernels yelling at them, no matter how real the
      error might be.  So only report it if CONFIG_KOBJECT_DEBUG is enabled.
      
      Sent on request of Andrew Morton.
      
      (akpm: should bring this back post-2.6.17)
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@suse.de>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      ae57a856
    • Alessandro Zummo's avatar
      [PATCH] rtc subsystem: use ENOIOCTLCMD and ENOTTY where appropriate · b3969e58
      Alessandro Zummo authored
      Appropriately use -ENOIOCTLCMD and -ENOTTY when the ioctl is not
      implemented by a driver.
      
      (akpm: we're not allowed to return -ENOIOCTLCMD to userspace.  This patch does
      the right thing).
      Signed-off-by: default avatarAlessandro Zummo <a.zummo@towertech.it>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      b3969e58
    • Atsushi Nemoto's avatar
      [PATCH] kbuild: fix modpost segfault for 64bit mipsel kernel · eae07ac6
      Atsushi Nemoto authored
      Here is an updated r_info layout fix.  Please apply "check SHT_REL
      sections" patch before this.
      
      64bit mips has different r_info layout.  This patch fixes modpost
      segfault for 64bit little endian mips kernel.
      Signed-off-by: default avatarAtsushi Nemoto <anemo@mba.ocn.ne.jp>
      Cc: Sam Ravnborg <sam@ravnborg.org>
      Cc: Ralf Baechle <ralf@linux-mips.org>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      eae07ac6
    • Atsushi Nemoto's avatar
      [PATCH] kbuild: check SHT_REL sections · 2c1a51f3
      Atsushi Nemoto authored
      I found that modpost can not detect section mismatch on mips and i386.  On
      mips64, the modpost (with r_info layout fix) can detect it.  The current
      modpst only checks SHT_RELA section but I suppose SHT_REL section should be
      checked also.  This patch does not contain r_info layout fix.  I'll post an
      updated r_info layout fix on next mail.
      
      Check SHT_REL sections as like as SHT_RELA sections to detect section
      mismatch.
      Signed-off-by: default avatarAtsushi Nemoto <anemo@mba.ocn.ne.jp>
      Cc: Sam Ravnborg <sam@ravnborg.org>
      Cc: Ralf Baechle <ralf@linux-mips.org>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      2c1a51f3
    • Martin Schwidefsky's avatar
      [PATCH] s390: next_timer_interrupt overflow in stop_hz_timer · 92f63cd0
      Martin Schwidefsky authored
      The 32 bit unsigned substraction (next - jiffies) in stop_hz_timer can
      overflow if jiffies gets advanced between next_timer_interrupt and the read
      under the xtime lock.  The cast to a u64 then results in a large value
      which causes the cpu to wait too long.  Fix this by casting next and
      jiffies independently to u64 before subtracting them.
      
      (Spotted by Zachary Amsden <zach@vmware.com>)
      Signed-off-by: default avatarMartin Schwidefsky <schwidefsky@de.ibm.com>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      92f63cd0
    • Zachary Amsden's avatar
      [PATCH] Fix a NO_IDLE_HZ timer bug · 0662b713
      Zachary Amsden authored
      Under certain timing conditions, a race during boot occurs where timer
      ticks are being processed on remote CPUs.  The remote timer ticks can
      increment jiffies, and if this happens during a window when a timeout is
      very close to expiring but a local tick has not yet been delivered, you can
      end up with
      
      1) No softirq pending
      2) A local timer wheel which is not synced to jiffies
      3) No high resolution timer active
      4) A local timer which is supposed to fire before the current jiffies value.
      
      In this circumstance, the comparison in next_timer_interrupt overflows,
      because the base of the comparison for high resolution timers is jiffies,
      but for the softirq timer wheel, it is relative the the current base of the
      wheel (jiffies_base).
      Signed-off-by: default avatarZachary Amsden <zach@vmware.com>
      Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>
      Cc: Oleg Nesterov <oleg@tv-sign.ru>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      0662b713
    • Rene Herman's avatar
      [PATCH] missing newline in scsi/st.c · 8b1ea24c
      Rene Herman authored
      st: Version 20050830, fixed bufsize 32768, s/g segs 256
      st 0:0:6:0: Attached scsi tape st0<4>st0: try direct i/o: yes (alignment 512 B)
      
      Cc: James Bottomley <James.Bottomley@steeleye.com>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      8b1ea24c
    • Satoshi Oshima's avatar
      [PATCH] kprobes: bad manipulation of 2 byte opcode on x86_64 · dc49e344
      Satoshi Oshima authored
      Problem:
      
      If we put a probe onto a callq instruction and the probe is executed,
      kernel panic of Bad RIP value occurs.
      
      Root cause:
      
      If resume_execution() found 0xff at first byte of p->ainsn.insn, it must
      check the _second_ byte.  But current resume_execution check _first_ byte
      again.
      
      I changed it checks second byte of p->ainsn.insn.
      
      Kprobes on i386 don't have this problem, because the implementation is a
      little bit different from x86_64.
      
      Cc: Andi Kleen <ak@muc.de>
      Signed-off-by: default avatarSatoshi Oshima <soshima@redhat.com>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      dc49e344