1. 24 7月, 2013 1 次提交
    • A
      USB: option: add D-Link DWM-152/C1 and DWM-156/C1 · ca247635
      Alexandr \"Sky\" Ivanov 提交于
      Adding support for D-Link DWM-152/C1 and DWM-156/C1 devices.
      
      DWM-152/C1:
      T:  Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  6 Spd=480 MxCh= 0
      D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
      P:  Vendor=07d1 ProdID=3e01 Rev= 0.00
      S:  Product=USB Configuration
      S:  SerialNumber=1234567890ABCDEF
      C:* #Ifs= 5 Cfg#= 1 Atr=e0 MxPwr=500mA
      I:* If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
      E:  Ad=81(I) Atr=03(Int.) MxPS=  64 Ivl=2ms
      E:  Ad=82(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
      E:  Ad=01(O) Atr=02(Bulk) MxPS= 512 Ivl=4ms
      I:* If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
      E:  Ad=83(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
      E:  Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=4ms
      I:* If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
      E:  Ad=84(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
      E:  Ad=03(O) Atr=02(Bulk) MxPS= 512 Ivl=4ms
      I:* If#= 3 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
      E:  Ad=85(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
      E:  Ad=04(O) Atr=02(Bulk) MxPS= 512 Ivl=4ms
      I:* If#= 4 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage
      E:  Ad=05(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
      E:  Ad=86(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
      
      DWM-156/C1:
      T:  Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  8 Spd=480 MxCh= 0
      D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
      P:  Vendor=07d1 ProdID=3e02 Rev= 0.00
      S:  Product=DataCard Device
      S:  SerialNumber=1234567890ABCDEF
      C:* #Ifs= 5 Cfg#= 1 Atr=e0 MxPwr=500mA
      I:* If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
      E:  Ad=81(I) Atr=03(Int.) MxPS=  64 Ivl=2ms
      E:  Ad=82(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
      E:  Ad=01(O) Atr=02(Bulk) MxPS= 512 Ivl=4ms
      I:* If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
      E:  Ad=83(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
      E:  Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=4ms
      I:* If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
      E:  Ad=84(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
      E:  Ad=03(O) Atr=02(Bulk) MxPS= 512 Ivl=4ms
      I:* If#= 3 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
      E:  Ad=85(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
      E:  Ad=04(O) Atr=02(Bulk) MxPS= 512 Ivl=4ms
      I:* If#= 4 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage
      E:  Ad=05(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
      E:  Ad=86(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
      Signed-off-by: NAlexandr Ivanov <alexandr.sky@gmail.com>
      Cc: stable <stable@vger.kernel.org>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      ca247635
  2. 23 7月, 2013 7 次提交
  3. 17 7月, 2013 3 次提交
    • A
      USB: global suspend and remote wakeup don't mix · e583d9db
      Alan Stern 提交于
      The hub driver was recently changed to use "global" suspend for system
      suspend transitions on non-SuperSpeed buses.  This means that we don't
      suspend devices individually by setting the suspend feature on the
      upstream hub port; instead devices all go into suspend automatically
      when the root hub stops transmitting packets.  The idea was to save
      time and to avoid certain kinds of wakeup races.
      
      Now it turns out that many hubs are buggy; they don't relay wakeup
      requests from a downstream port to their upstream port if the
      downstream port's suspend feature is not set (depending on the speed
      of the downstream port, whether or not the hub is enabled for remote
      wakeup, and possibly other factors).
      
      We can't have hubs dropping wakeup requests.  Therefore this patch
      goes partway back to the old policy: It sets the suspend feature for a
      port if the device attached to that port or any of its descendants is
      enabled for wakeup.  People will still be able to benefit from the
      time savings if they don't care about wakeup and leave it disabled on
      all their devices.
      
      In order to accomplish this, the patch adds a new field to the usb_hub
      structure: wakeup_enabled_descendants is a count of how many devices
      below a suspended hub are enabled for remote wakeup.  A corresponding
      new subroutine determines the number of wakeup-enabled devices at or
      below an arbitrary suspended USB device.
      
      This should be applied to the 3.10 stable kernel.
      Signed-off-by: NAlan Stern <stern@rowland.harvard.edu>
      Reported-and-tested-by: NToralf Förster <toralf.foerster@gmx.de>
      Cc: stable <stable@vger.kernel.org>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      e583d9db
    • A
      USB: move the definition of USB_MAXCHILDREN · 36ff66db
      Alan Stern 提交于
      The USB_MAXCHILDREN symbol is used in include/uapi/linux/usb/ch11.h, a
      user-mode header, even though it is defined in include/linux/usb.h,
      which is kernel-only.  This causes compile-time errors when user
      programs try to #include linux/usb/ch11.h.
      
      This patch fixes the problem by moving the definition of USB_MAXCHILDREN
      into ch11.h.  It also gets rid of unneeded parentheses.
      Signed-off-by: NAlan Stern <stern@rowland.harvard.edu>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      36ff66db
    • G
      Merge tag 'fixes-for-v3.11-rc1' of... · 39c24270
      Greg Kroah-Hartman 提交于
      Merge tag 'fixes-for-v3.11-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb into usb-linus
      
      Felipe writes:
      
      usb: fixes for v3.11-rc1
      
      Quite a few changes going on here. They have been
      boot tested on OMAP5 and compile tested on ARM and x86
      with different defconfigs.
      
      Many gadget drivers got a depends on HAS_DMA in order
      to prevent build failures on !HAS_DMA architectures.
      
      DWC3 learned how to allow a gadget driver to be modprobed
      after an unsuccessful modprobe of another gadget driver. It
      also got a fix to a wrong bit mask in dwc3_event_type, and
      learns to return proper error codes from failed usb3_phy
      initialization.
      
      RNDIS function driver can now be built with configfs.
      
      at91_udc now knows that we need to prepare the clock
      before enabling it.
      
      renesas_usbhs now lets gadget drivers be modprobed
      multiple times.
      
      phy-omap-usb3 got a fix for the DPLL settings.
      
      mv_u3d_core now passes the correct cookie to free_irq().
      
      fotg210-udc got Section mismatch fixes.
      Signed-of-by: NFelipe Balbi <balbi@ti.com>
      39c24270
  4. 15 7月, 2013 20 次提交
    • R
      usb: phy: omap-usb3: fix dpll clock index · 690c70ba
      Ruchika Kharwar 提交于
      Correction of the omap_usb3_dpll_params array when the sys_clk_rate is
      20MHz.
      Signed-off-by: NNikhil Devshatwar <nikhil.nd@ti.com>
      Signed-off-by: NRuchika Kharwar <ruchika@ti.com>
      Signed-off-by: NFelipe Balbi <balbi@ti.com>
      690c70ba
    • S
      usb: phy: samsung: Fix an error message typo · 24e6bfd9
      Sachin Kamat 提交于
      The error message is common to both clk_get functions. Update it
      accordingly.
      Signed-off-by: NSachin Kamat <sachin.kamat@linaro.org>
      Signed-off-by: NFelipe Balbi <balbi@ti.com>
      24e6bfd9
    • A
      usb: gadget: don't fail when DMA isn't present · 908b9613
      Alan Stern 提交于
      When CONFIG_HAS_DMA isn't enabled, the UDC core gets build errors:
      
      drivers/built-in.o: In function `dma_set_coherent_mask':
      include/linux/dma-mapping.h:93: undefined reference to `dma_supported'
      include/linux/dma-mapping.h:93: undefined reference to `dma_supported'
      drivers/built-in.o: In function `usb_gadget_unmap_request':
      drivers/usb/gadget/udc-core.c:91: undefined reference to `dma_unmap_sg'
      drivers/usb/gadget/udc-core.c:96: undefined reference to `dma_unmap_single'
      drivers/built-in.o: In function `usb_gadget_map_request':
      drivers/usb/gadget/udc-core.c:62: undefined reference to `dma_map_sg'
      drivers/usb/gadget/udc-core.c:71: undefined reference to `dma_map_single'
      drivers/usb/gadget/udc-core.c:74: undefined reference to `dma_mapping_error'
      
      Prevent this by protecting the DMA API routines with preprocessor tests.
      Signed-off-by: NAlan Stern <stern@rowland.harvard.edu>
      CC: Geert Uytterhoeven <geert@linux-m68k.org>
      Acked-by: NAlexander Shishkin <alexander.shishkin@linux.intel.com>
      Signed-off-by: NFelipe Balbi <balbi@ti.com>
      908b9613
    • G
      usb: gadget: USB_MV_U3D should depend on HAS_DMA · 91f6b847
      Geert Uytterhoeven 提交于
      If NO_DMA=y:
      
      drivers/built-in.o: In function `mv_u3d_done':
      drivers/usb/gadget/mv_u3d_core.c:206: undefined reference to `dma_pool_free'
      drivers/usb/gadget/mv_u3d_core.c:209: undefined reference to `dma_unmap_single'
      drivers/built-in.o: In function `mv_u3d_build_trb_one':
      drivers/usb/gadget/mv_u3d_core.c:311: undefined reference to `dma_pool_alloc'
      drivers/built-in.o: In function `mv_u3d_req_to_trb':
      drivers/usb/gadget/mv_u3d_core.c:480: undefined reference to `dma_map_single'
      drivers/built-in.o: In function `mv_u3d_remove':
      drivers/usb/gadget/mv_u3d_core.c:1770: undefined reference to `dma_pool_destroy'
      drivers/usb/gadget/mv_u3d_core.c:1773: undefined reference to `dma_free_coherent'
      drivers/built-in.o: In function `mv_u3d_probe':
      drivers/usb/gadget/mv_u3d_core.c:1880: undefined reference to `dma_alloc_coherent'
      drivers/usb/gadget/mv_u3d_core.c:1890: undefined reference to `dma_pool_create'
      drivers/usb/gadget/mv_u3d_core.c:1984: undefined reference to `dma_pool_destroy'
      drivers/usb/gadget/mv_u3d_core.c:1986: undefined reference to `dma_free_coherent'
      Signed-off-by: NGeert Uytterhoeven <geert@linux-m68k.org>
      Signed-off-by: NFelipe Balbi <balbi@ti.com>
      91f6b847
    • G
      usb: gadget: USB_FOTG210_UDC should depend on HAS_DMA · bfcbd020
      Geert Uytterhoeven 提交于
      If NO_DMA=y:
      
      drivers/built-in.o: In function `fotg210_start_dma':
      drivers/usb/gadget/fotg210-udc.c:354: undefined reference to `dma_map_single'
      drivers/usb/gadget/fotg210-udc.c:357: undefined reference to `dma_mapping_error'
      drivers/usb/gadget/fotg210-udc.c:362: undefined reference to `dma_sync_single_for_cpu'
      drivers/usb/gadget/fotg210-udc.c:376: undefined reference to `dma_unmap_single'
      Signed-off-by: NGeert Uytterhoeven <geert@linux-m68k.org>
      Signed-off-by: NFelipe Balbi <balbi@ti.com>
      bfcbd020
    • G
      usb: gadget: USB_MV_UDC should depend on HAS_DMA · 4713aec1
      Geert Uytterhoeven 提交于
      If NO_DMA=y:
      
      drivers/built-in.o: In function `done':
      drivers/usb/gadget/mv_udc_core.c:239: undefined reference to `dma_pool_free'
      drivers/built-in.o: In function `build_dtd':
      drivers/usb/gadget/mv_udc_core.c:371: undefined reference to `dma_pool_alloc'
      drivers/built-in.o: In function `udc_prime_status':
      drivers/usb/gadget/mv_udc_core.c:1465: undefined reference to `dma_map_single'
      drivers/built-in.o: In function `mv_udc_remove':
      drivers/usb/gadget/mv_udc_core.c:2087: undefined reference to `dma_pool_destroy'
      drivers/usb/gadget/mv_udc_core.c:2090: undefined reference to `dma_free_coherent'
      drivers/built-in.o: In function `mv_udc_probe':
      drivers/usb/gadget/mv_udc_core.c:2190: undefined reference to `dma_alloc_coherent'
      drivers/usb/gadget/mv_udc_core.c:2201: undefined reference to `dma_pool_create'
      drivers/usb/gadget/mv_udc_core.c:2315: undefined reference to `dma_pool_destroy'
      drivers/usb/gadget/mv_udc_core.c:2317: undefined reference to `dma_free_coherent'
      Signed-off-by: NGeert Uytterhoeven <geert@linux-m68k.org>
      Signed-off-by: NFelipe Balbi <balbi@ti.com>
      4713aec1
    • G
      usb: dwc3: USB_DWC3 should depend on HAS_DMA · 8744303e
      Geert Uytterhoeven 提交于
      If NO_DMA=y:
      
      drivers/built-in.o: In function `dwc3_free_one_event_buffer':
      drivers/usb/dwc3/core.c:132: undefined reference to `dma_free_coherent'
      drivers/built-in.o: In function `dwc3_alloc_one_event_buffer':
      drivers/usb/dwc3/core.c:154: undefined reference to `dma_alloc_coherent'
      drivers/built-in.o: In function `dma_set_coherent_mask':
      include/linux/dma-mapping.h:93: undefined reference to `dma_supported'
      drivers/built-in.o: In function `dwc3_free_trb_pool':
      drivers/usb/dwc3/gadget.c:407: undefined reference to `dma_free_coherent'
      drivers/built-in.o: In function `dwc3_gadget_exit':
      drivers/usb/dwc3/gadget.c:2693: undefined reference to `dma_free_coherent'
      drivers/built-in.o: In function `dwc3_alloc_trb_pool':
      drivers/usb/dwc3/gadget.c:391: undefined reference to `dma_alloc_coherent'
      drivers/built-in.o: In function `dwc3_gadget_init':
      drivers/usb/dwc3/gadget.c:2598: undefined reference to `dma_alloc_coherent'
      drivers/usb/dwc3/gadget.c:2667: undefined reference to `dma_free_coherent'
      drivers/usb/dwc3/gadget.c:2674: undefined reference to `dma_free_coherent'
      drivers/usb/dwc3/gadget.c:2678: undefined reference to `dma_free_coherent'
      Signed-off-by: NGeert Uytterhoeven <geert@linux-m68k.org>
      Signed-off-by: NFelipe Balbi <balbi@ti.com>
      8744303e
    • A
      usb: gadget: Kconfig: Fix configfs-based RNDIS function build · 9d140f79
      Andrzej Pietrasiewicz 提交于
      USB_CONFIGFS_RNDIS depends on USB_U_RNDIS. Select it.
      Acked-by: NMichal Nazarewicz <mina86@mina86.com>
      Reported-by: NFengguang Wu <fengguang.wu@intel.com>
      Signed-off-by: NAndrzej Pietrasiewicz <andrzej.p@samsung.com>
      Signed-off-by: NKyungmin Park <kyungmin.park@samsung.com>
      Signed-off-by: NFelipe Balbi <balbi@ti.com>
      9d140f79
    • K
      usb: renesas_usbhs: gadget: remove extra check on udc_stop · 8047806e
      Kuninori Morimoto 提交于
      usb_gadget_ops :: udc_stop might be called with driver = NULL since
      511f3c53
      (usb: gadget: udc-core: fix a regression during gadget driver unbinding)
      
      Because of that, 2nd times insmod goes fail.
      This patch fixes it up.
      Reported-by: NYusuke Goda <yusuke.goda.sx@renesas.com>
      Signed-off-by: NKuninori Morimoto <kuninori.morimoto.gx@renesas.com>
      Signed-off-by: NFelipe Balbi <balbi@ti.com>
      8047806e
    • W
      usb: gadget: mv_u3d_core: fix to pass correct device identity to free_irq() · 5257a633
      Wei Yongjun 提交于
      free_irq() expects the same device identity that was passed to
      corresponding request_irq(), otherwise the IRQ is not freed.
      Signed-off-by: NWei Yongjun <yongjun_wei@trendmicro.com.cn>
      Signed-off-by: NFelipe Balbi <balbi@ti.com>
      5257a633
    • R
      usb: dwc3: fix the error returned with usb3_phy failure · 315955d7
      Ruchika Kharwar 提交于
      When there is an error with the usb3_phy probe or absence, the error returned
      is erroneously for usb2_phy.
      
      Cc: <stable@vger.kernel.org>
      Signed-off-by: NRuchika Kharwar <ruchika@ti.com>
      Signed-off-by: NFelipe Balbi <balbi@ti.com>
      315955d7
    • H
      usb: dwc3: fix wrong bit mask in dwc3_event_type · 1974d494
      Huang Rui 提交于
      Per dwc3 2.50a spec, the is_devspec bit is used to distinguish the
      Device Endpoint-Specific Event or Device-Specific Event (DEVT). If the
      bit is 1, the event is represented Device-Specific Event, then use
      [7:1] bits as Device Specific Event to marked the type. It has 7 bits,
      and we can see the reserved8_31 variable name which means from 8 to 31
      bits marked reserved, actually there are 24 bits not 25 bits between
      that. And 1 + 7 + 24 = 32, the event size is 4 byes.
      
      So in dwc3_event_type, the bit mask should be:
      is_devspec	[0]		1  bit
      type		[7:1]		7  bits
      reserved8_31	[31:8]		24 bits
      
      This patch should be backported to kernels as old as 3.2, that contain
      the commit 72246da4 "usb: Introduce
      DesignWare USB3 DRD Driver".
      
      Cc: <stable@vger.kernel.org>
      Signed-off-by: NHuang Rui <ray.huang@amd.com>
      Signed-off-by: NFelipe Balbi <balbi@ti.com>
      1974d494
    • B
      usb: gadget: at91_udc: prepare clk before calling enable · 76280832
      Boris BREZILLON 提交于
      Replace clk_enable/disable with clk_prepare_enable/disable_unprepare to
      avoid common clk framework warnings.
      Signed-off-by: NBoris BREZILLON <b.brezillon@overkiz.com>
      Signed-off-by: NFelipe Balbi <balbi@ti.com>
      76280832
    • Y
      usb: gadget: fotg210-udc: remove __init and __exit · 88ae7423
      Yuan-Hsin Chen 提交于
      Remove __init and __exit from probe() and remove() and
      would also fix the section mismatch issue.
      Signed-off-by: NYuan-Hsin Chen <yhchen@faraday-tech.com>
      Signed-off-by: NFelipe Balbi <balbi@ti.com>
      88ae7423
    • A
      usb: gadget: at91_udc: call at91udc_of_init only when needed · ae40d64b
      Arnd Bergmann 提交于
      This avoids a build error in at91sam9261_9g10_defconfig:
      
      drivers/usb/gadget/at91_udc.c: In function 'at91udc_probe':
      drivers/usb/gadget/at91_udc.c:1685:34: warning: 'flags' may be used uninitialized in this
      function [-Wmaybe-uninitialized]
        board->vbus_active_low = (flags & OF_GPIO_ACTIVE_LOW) ? 1 : 0;
                                        ^
      drivers/usb/gadget/at91_udc.c:1678:21: note: 'flags' was declared here
        enum of_gpio_flags flags;
                           ^
      
      Making the call to at91udc_of_init conditinal also reduces
      the object code size without sacrificing build coverage.
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      Cc: Felipe Balbi <balbi@ti.com>
      Cc: Nicolas Ferre <nicolas.ferre@atmel.com>
      Signed-off-by: NFelipe Balbi <balbi@ti.com>
      ae40d64b
    • F
      usb: dwc3: gadget: don't prevent gadget from being probed if we fail · cdcedd69
      Felipe Balbi 提交于
      In case we fail our ->udc_start() callback, we
      should be ready to accept another modprobe following
      the failed one.
      
      We had forgotten to clear dwc->gadget_driver back
      to NULL and, because of that, we were preventing
      gadget driver modprobe from being retried.
      
      Cc: <stable@vger.kernel.org>
      Signed-off-by: NFelipe Balbi <balbi@ti.com>
      cdcedd69
    • L
      Linux 3.11-rc1 · ad81f054
      Linus Torvalds 提交于
      ad81f054
    • L
      Merge branch 'slab/for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/penberg/linux · 54be8200
      Linus Torvalds 提交于
      Pull slab update from Pekka Enberg:
       "Highlights:
      
        - Fix for boot-time problems on some architectures due to
          init_lock_keys() not respecting kmalloc_caches boundaries
          (Christoph Lameter)
      
        - CONFIG_SLUB_CPU_PARTIAL requested by RT folks (Joonsoo Kim)
      
        - Fix for excessive slab freelist draining (Wanpeng Li)
      
        - SLUB and SLOB cleanups and fixes (various people)"
      
      I ended up editing the branch, and this avoids two commits at the end
      that were immediately reverted, and I instead just applied the oneliner
      fix in between myself.
      
      * 'slab/for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/penberg/linux
        slub: Check for page NULL before doing the node_match check
        mm/slab: Give s_next and s_stop slab-specific names
        slob: Check for NULL pointer before calling ctor()
        slub: Make cpu partial slab support configurable
        slab: add kmalloc() to kernel API documentation
        slab: fix init_lock_keys
        slob: use DIV_ROUND_UP where possible
        slub: do not put a slab to cpu partial list when cpu_partial is 0
        mm/slub: Use node_nr_slabs and node_nr_objs in get_slabinfo
        mm/slub: Drop unnecessary nr_partials
        mm/slab: Fix /proc/slabinfo unwriteable for slab
        mm/slab: Sharing s_next and s_stop between slab and slub
        mm/slab: Fix drain freelist excessively
        slob: Rework #ifdeffery in slab.h
        mm, slab: moved kmem_cache_alloc_node comment to correct place
      54be8200
    • S
      slub: Check for page NULL before doing the node_match check · c25f195e
      Steven Rostedt 提交于
      In the -rt kernel (mrg), we hit the following dump:
      
      BUG: unable to handle kernel NULL pointer dereference at           (null)
      IP: [<ffffffff811573f1>] kmem_cache_alloc_node+0x51/0x180
      PGD a2d39067 PUD b1641067 PMD 0
      Oops: 0000 [#1] PREEMPT SMP
      Modules linked in: sunrpc cpufreq_ondemand ipv6 tg3 joydev sg serio_raw pcspkr k8temp amd64_edac_mod edac_core i2c_piix4 e100 mii shpchp ext4 mbcache jbd2 sd_mod crc_t10dif sr_mod cdrom sata_svw ata_generic pata_acpi pata_serverworks radeon ttm drm_kms_helper drm hwmon i2c_algo_bit i2c_core dm_mirror dm_region_hash dm_log dm_mod
      CPU 3
      Pid: 20878, comm: hackbench Not tainted 3.6.11-rt25.14.el6rt.x86_64 #1 empty empty/Tyan Transport GT24-B3992
      RIP: 0010:[<ffffffff811573f1>]  [<ffffffff811573f1>] kmem_cache_alloc_node+0x51/0x180
      RSP: 0018:ffff8800a9b17d70  EFLAGS: 00010213
      RAX: 0000000000000000 RBX: 0000000001200011 RCX: ffff8800a06d8000
      RDX: 0000000004d92a03 RSI: 00000000000000d0 RDI: ffff88013b805500
      RBP: ffff8800a9b17dc0 R08: ffff88023fd14d10 R09: ffffffff81041cbd
      R10: 00007f4e3f06e9d0 R11: 0000000000000246 R12: ffff88013b805500
      R13: ffff8801ff46af40 R14: 0000000000000001 R15: 0000000000000000
      FS:  00007f4e3f06e700(0000) GS:ffff88023fd00000(0000) knlGS:0000000000000000
      CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
      CR2: 0000000000000000 CR3: 00000000a2d3a000 CR4: 00000000000007e0
      DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
      DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
      Process hackbench (pid: 20878, threadinfo ffff8800a9b16000, task ffff8800a06d8000)
      Stack:
       ffff8800a9b17da0 ffffffff81202e08 ffff8800a9b17de0 000000d001200011
       0000000001200011 0000000001200011 0000000000000000 0000000000000000
       00007f4e3f06e9d0 0000000000000000 ffff8800a9b17e60 ffffffff81041cbd
      Call Trace:
       [<ffffffff81202e08>] ? current_has_perm+0x68/0x80
       [<ffffffff81041cbd>] copy_process+0xdd/0x15b0
       [<ffffffff810a2125>] ? rt_up_read+0x25/0x30
       [<ffffffff8104369a>] do_fork+0x5a/0x360
       [<ffffffff8107c66b>] ? migrate_enable+0xeb/0x220
       [<ffffffff8100b068>] sys_clone+0x28/0x30
       [<ffffffff81527423>] stub_clone+0x13/0x20
       [<ffffffff81527152>] ? system_call_fastpath+0x16/0x1b
      Code: 89 fc 89 75 cc 41 89 d6 4d 8b 04 24 65 4c 03 04 25 48 ae 00 00 49 8b 50 08 4d 8b 28 49 8b 40 10 4d 85 ed 74 12 41 83 fe ff 74 27 <48> 8b 00 48 c1 e8 3a 41 39 c6 74 1b 8b 75 cc 4c 89 c9 44 89 f2
      RIP  [<ffffffff811573f1>] kmem_cache_alloc_node+0x51/0x180
       RSP <ffff8800a9b17d70>
      CR2: 0000000000000000
      ---[ end trace 0000000000000002 ]---
      
      Now, this uses SLUB pretty much unmodified, but as it is the -rt kernel
      with CONFIG_PREEMPT_RT set, spinlocks are mutexes, although they do
      disable migration. But the SLUB code is relatively lockless, and the
      spin_locks there are raw_spin_locks (not converted to mutexes), thus I
      believe this bug can happen in mainline without -rt features. The -rt
      patch is just good at triggering mainline bugs ;-)
      
      Anyway, looking at where this crashed, it seems that the page variable
      can be NULL when passed to the node_match() function (which does not
      check if it is NULL). When this happens we get the above panic.
      
      As page is only used in slab_alloc() to check if the node matches, if
      it's NULL I'm assuming that we can say it doesn't and call the
      __slab_alloc() code. Is this a correct assumption?
      Acked-by: NChristoph Lameter <cl@linux.com>
      Signed-off-by: NSteven Rostedt <rostedt@goodmis.org>
      Signed-off-by: NPekka Enberg <penberg@kernel.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      c25f195e
    • L
      Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs · 41d9884c
      Linus Torvalds 提交于
      Pull more vfs stuff from Al Viro:
       "O_TMPFILE ABI changes, Oleg's fput() series, misc cleanups, including
        making simple_lookup() usable for filesystems with non-NULL s_d_op,
        which allows us to get rid of quite a bit of ugliness"
      
      * 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs:
        sunrpc: now we can just set ->s_d_op
        cgroup: we can use simple_lookup() now
        efivarfs: we can use simple_lookup() now
        make simple_lookup() usable for filesystems that set ->s_d_op
        configfs: don't open-code d_alloc_name()
        __rpc_lookup_create_exclusive: pass string instead of qstr
        rpc_create_*_dir: don't bother with qstr
        llist: llist_add() can use llist_add_batch()
        llist: fix/simplify llist_add() and llist_add_batch()
        fput: turn "list_head delayed_fput_list" into llist_head
        fs/file_table.c:fput(): add comment
        Safer ABI for O_TMPFILE
      41d9884c
  5. 14 7月, 2013 9 次提交