1. 04 7月, 2019 1 次提交
  2. 01 7月, 2019 1 次提交
  3. 21 6月, 2019 1 次提交
  4. 20 6月, 2019 1 次提交
    • Y
      doc: fix documentation about UIO_MEM_LOGICAL using · 6ad805b8
      Yang Yingliang 提交于
      After commit d4fc5069 ("mm: switch s_mem and slab_cache in struct page")
      page->mapping will be re-used by slab allocations and page->mapping->host
      will be used in balance_dirty_pages_ratelimited() as an inode member but
      it's not an inode in fact and leads an oops.
      
      [  159.906493] Unable to handle kernel paging request at virtual address ffff200012d90be8
      [  159.908029] Mem abort info:
      [  159.908552]   ESR = 0x96000007
      [  159.909138]   Exception class = DABT (current EL), IL = 32 bits
      [  159.910155]   SET = 0, FnV = 0
      [  159.910690]   EA = 0, S1PTW = 0
      [  159.911241] Data abort info:
      [  159.911846]   ISV = 0, ISS = 0x00000007
      [  159.912567]   CM = 0, WnR = 0
      [  159.913105] swapper pgtable: 4k pages, 48-bit VAs, pgdp=0000000042acd000
      [  159.914269] [ffff200012d90be8] pgd=000000043ffff003, pud=000000043fffe003, pmd=000000043fffa003, pte=0000000000000000
      [  159.916280] Internal error: Oops: 96000007 [#1] SMP
      [  159.917195] Dumping ftrace buffer:
      [  159.917845]    (ftrace buffer empty)
      [  159.918521] Modules linked in: uio_dev(OE)
      [  159.919276] CPU: 1 PID: 295 Comm: uio_test Tainted: G           OE     5.2.0-rc4+ #46
      [  159.920859] Hardware name: linux,dummy-virt (DT)
      [  159.921815] pstate: 60000005 (nZCv daif -PAN -UAO)
      [  159.922809] pc : balance_dirty_pages_ratelimited+0x68/0xc38
      [  159.923965] lr : fault_dirty_shared_page.isra.8+0xe4/0x100
      [  159.925134] sp : ffff800368a77ae0
      [  159.925824] x29: ffff800368a77ae0 x28: 1ffff0006d14ce1a
      [  159.926906] x27: ffff800368a670d0 x26: ffff800368a67120
      [  159.927985] x25: 1ffff0006d10f5fe x24: ffff200012d90be8
      [  159.929089] x23: ffff200013732000 x22: ffff80036ec03200
      [  159.930172] x21: ffff200012d90bc0 x20: 1fffe400025b217d
      [  159.931253] x19: ffff80036ec03200 x18: 0000000000000000
      [  159.932348] x17: 0000000000000000 x16: 0ffffe0000010208
      [  159.933439] x15: 0000000000000000 x14: 0000000000000000
      [  159.934518] x13: 0000000000000000 x12: 0000000000000000
      [  159.935596] x11: 1fffefc001b452c0 x10: ffff0fc001b452c0
      [  159.936697] x9 : dfff200000000000 x8 : dfff200000000001
      [  159.937781] x7 : ffff7e000da29607 x6 : ffff0fc001b452c1
      [  159.938859] x5 : ffff0fc001b452c1 x4 : ffff0fc001b452c1
      [  159.939944] x3 : ffff200010523ad4 x2 : 1fffe400026e659b
      [  159.941065] x1 : dfff200000000000 x0 : ffff200013732cd8
      [  159.942205] Call trace:
      [  159.942732]  balance_dirty_pages_ratelimited+0x68/0xc38
      [  159.943797]  fault_dirty_shared_page.isra.8+0xe4/0x100
      [  159.944867]  do_fault+0x608/0x1250
      [  159.945571]  __handle_mm_fault+0x93c/0xfb8
      [  159.946412]  handle_mm_fault+0x1c0/0x360
      [  159.947224]  do_page_fault+0x358/0x8d0
      [  159.947993]  do_translation_fault+0xf8/0x124
      [  159.948884]  do_mem_abort+0x70/0x190
      [  159.949624]  el0_da+0x24/0x28
      
      According another commit 5e901d0b ("scsi: qedi: Fix bad pte call trace
      when iscsiuio is stopped."), using kmalloc also cause other problem.
      
      But the documentation about UIO_MEM_LOGICAL allows using kmalloc(), remove
      and don't allow using kmalloc() in documentation.
      Signed-off-by: NYang Yingliang <yangyingliang@huawei.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      6ad805b8
  5. 15 6月, 2019 2 次提交
  6. 14 6月, 2019 1 次提交
  7. 11 6月, 2019 1 次提交
    • M
      docs: s390: convert docs to ReST and rename to *.rst · 8b4a503d
      Mauro Carvalho Chehab 提交于
      Convert all text files with s390 documentation to ReST format.
      
      Tried to preserve as much as possible the original document
      format. Still, some of the files required some work in order
      for it to be visible on both plain text and after converted
      to html.
      
      The conversion is actually:
        - add blank lines and identation in order to identify paragraphs;
        - fix tables markups;
        - add some lists markups;
        - mark literal blocks;
        - adjust title markups.
      
      At its new index.rst, let's add a :orphan: while this is not linked to
      the main index.rst file, in order to avoid build warnings.
      Signed-off-by: NMauro Carvalho Chehab <mchehab+samsung@kernel.org>
      Signed-off-by: NHeiko Carstens <heiko.carstens@de.ibm.com>
      8b4a503d
  8. 09 6月, 2019 1 次提交
  9. 08 6月, 2019 2 次提交
  10. 06 6月, 2019 7 次提交
  11. 04 6月, 2019 1 次提交
  12. 28 5月, 2019 2 次提交
  13. 25 5月, 2019 4 次提交
  14. 21 5月, 2019 1 次提交
  15. 07 5月, 2019 1 次提交
  16. 26 4月, 2019 4 次提交
  17. 20 4月, 2019 1 次提交
    • A
      USB: core: Fix bug caused by duplicate interface PM usage counter · c2b71462
      Alan Stern 提交于
      The syzkaller fuzzer reported a bug in the USB hub driver which turned
      out to be caused by a negative runtime-PM usage counter.  This allowed
      a hub to be runtime suspended at a time when the driver did not expect
      it.  The symptom is a WARNING issued because the hub's status URB is
      submitted while it is already active:
      
      	URB 0000000031fb463e submitted while active
      	WARNING: CPU: 0 PID: 2917 at drivers/usb/core/urb.c:363
      
      The negative runtime-PM usage count was caused by an unfortunate
      design decision made when runtime PM was first implemented for USB.
      At that time, USB class drivers were allowed to unbind from their
      interfaces without balancing the usage counter (i.e., leaving it with
      a positive count).  The core code would take care of setting the
      counter back to 0 before allowing another driver to bind to the
      interface.
      
      Later on when runtime PM was implemented for the entire kernel, the
      opposite decision was made: Drivers were required to balance their
      runtime-PM get and put calls.  In order to maintain backward
      compatibility, however, the USB subsystem adapted to the new
      implementation by keeping an independent usage counter for each
      interface and using it to automatically adjust the normal usage
      counter back to 0 whenever a driver was unbound.
      
      This approach involves duplicating information, but what is worse, it
      doesn't work properly in cases where a USB class driver delays
      decrementing the usage counter until after the driver's disconnect()
      routine has returned and the counter has been adjusted back to 0.
      Doing so would cause the usage counter to become negative.  There's
      even a warning about this in the USB power management documentation!
      
      As it happens, this is exactly what the hub driver does.  The
      kick_hub_wq() routine increments the runtime-PM usage counter, and the
      corresponding decrement is carried out by hub_event() in the context
      of the hub_wq work-queue thread.  This work routine may sometimes run
      after the driver has been unbound from its interface, and when it does
      it causes the usage counter to go negative.
      
      It is not possible for hub_disconnect() to wait for a pending
      hub_event() call to finish, because hub_disconnect() is called with
      the device lock held and hub_event() acquires that lock.  The only
      feasible fix is to reverse the original design decision: remove the
      duplicate interface-specific usage counter and require USB drivers to
      balance their runtime PM gets and puts.  As far as I know, all
      existing drivers currently do this.
      Signed-off-by: NAlan Stern <stern@rowland.harvard.edu>
      Reported-and-tested-by: syzbot+7634edaea4d0b341c625@syzkaller.appspotmail.com
      CC: <stable@vger.kernel.org>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      c2b71462
  18. 08 4月, 2019 3 次提交
  19. 02 4月, 2019 1 次提交
  20. 05 3月, 2019 1 次提交
  21. 20 2月, 2019 1 次提交
  22. 19 2月, 2019 1 次提交
  23. 14 2月, 2019 1 次提交