Skip to content

cloud-kernel
cloud-kernel

openanolis / cloud-kernel
大约 1 年 前同步成功

通知 158
Star 36
Fork 7
cloud-kernel
cloud-kernel

体验新版 GitCode，发现更多精彩内容 >>

切换分支/标签
  1. 26 4月, 2018 5 次提交
  3. 12 2月, 2018 1 次提交
    • L
      vfs: do bulk POLL* -> EPOLL* replacement · a9a08845
      由 Linus Torvalds 提交于 
      This is the mindless scripted replacement of kernel use of POLL*
variables as described by Al, done by this script:

    for V in IN OUT PRI ERR RDNORM RDBAND WRNORM WRBAND HUP RDHUP NVAL MSG; do
        L=`git grep -l -w POLL$V | grep -v '^t' | grep -v /um/ | grep -v '^sa' | grep -v '/poll.h$'|grep -v '^D'`
        for f in $L; do sed -i "-es/^\([^\"]*\)\(\<POLL$V\>\)/\\1E\\2/" $f; done
    done

with de-mangling cleanups yet to come.

NOTE! On almost all architectures, the EPOLL* constants have the same
values as the POLL* constants do.  But they keyword here is "almost".
For various bad reasons they aren't the same, and epoll() doesn't
actually work quite correctly in some cases due to this on Sparc et al.

The next patch from Al will sort out the final differences, and we
should be all done.
Scripted-by: NAl Viro <viro@zeniv.linux.org.uk>
Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      a9a08845
  5. 29 11月, 2017 1 次提交
  7. 01 9月, 2017 1 次提交
  9. 28 8月, 2017 1 次提交
  11. 24 8月, 2017 1 次提交
  13. 03 5月, 2017 1 次提交
  15. 07 4月, 2017 1 次提交
  17. 17 3月, 2017 1 次提交
  19. 02 3月, 2017 1 次提交
  21. 28 2月, 2017 1 次提交
  23. 20 1月, 2017 1 次提交
  25. 15 12月, 2016 1 次提交
  27. 31 10月, 2016 1 次提交
    • M
      virtio: console: Unlock vqs while freeing buffers · 34563769
      由 Matt Redfearn 提交于 
      Commit c6017e79 ("virtio: console: add locks around buffer removal
in port unplug path") added locking around the freeing of buffers in the
vq. However, when free_buf() is called with can_sleep = true and rproc
is enabled, it calls dma_free_coherent() directly, requiring interrupts
to be enabled. Currently a WARNING is triggered due to the spin locking
around free_buf, with a call stack like this:

WARNING: CPU: 3 PID: 121 at ./include/linux/dma-mapping.h:433
free_buf+0x1a8/0x288
Call Trace:
[<8040c538>] show_stack+0x74/0xc0
[<80757240>] dump_stack+0xd0/0x110
[<80430d98>] __warn+0xfc/0x130
[<80430ee0>] warn_slowpath_null+0x2c/0x3c
[<807e7c6c>] free_buf+0x1a8/0x288
[<807ea590>] remove_port_data+0x50/0xac
[<807ea6a0>] unplug_port+0xb4/0x1bc
[<807ea858>] virtcons_remove+0xb0/0xfc
[<807b6734>] virtio_dev_remove+0x58/0xc0
[<807f918c>] __device_release_driver+0xac/0x134
[<807f924c>] device_release_driver+0x38/0x50
[<807f7edc>] bus_remove_device+0xfc/0x130
[<807f4b74>] device_del+0x17c/0x21c
[<807f4c38>] device_unregister+0x24/0x38
[<807b6b50>] unregister_virtio_device+0x28/0x44

Fix this by restructuring the loops to allow the locks to only be taken
where it is necessary to protect the vqs, and release it while the
buffer is being freed.

Fixes: c6017e79 ("virtio: console: add locks around buffer removal in port unplug path")
Cc: stable@vger.kernel.org
Signed-off-by: NMatt Redfearn <matt.redfearn@imgtec.com>
Signed-off-by: NMichael S. Tsirkin <mst@redhat.com>
      34563769
  29. 12 10月, 2016 1 次提交
  31. 06 10月, 2016 1 次提交
  33. 10 9月, 2016 1 次提交
  35. 08 9月, 2016 1 次提交
  37. 25 5月, 2015 1 次提交
  39. 03 4月, 2015 1 次提交
  41. 05 3月, 2015 2 次提交
  43. 11 2月, 2015 1 次提交
  45. 04 2月, 2015 1 次提交
  47. 21 1月, 2015 1 次提交
  49. 09 12月, 2014 4 次提交
  51. 13 11月, 2014 1 次提交
  53. 15 10月, 2014 2 次提交
  55. 27 7月, 2014 1 次提交
  57. 02 4月, 2014 1 次提交
  59. 10 2月, 2014 1 次提交
    • A
      fix a kmap leak in virtio_console · c9efe511
      由 Al Viro 提交于 
      While we are at it, don't do kmap() under kmap_atomic(), *especially*
for a page we'd allocated with GFP_KERNEL.  It's spelled "page_address",
and had that been more than that, we'd have a real trouble - kmap_high()
can block, and doing that while holding kmap_atomic() is a Bad Idea(tm).
Signed-off-by: NAl Viro <viro@zeniv.linux.org.uk>
      c9efe511
  61. 29 10月, 2013 1 次提交