1. 10 12月, 2020 28 次提交
  2. 24 11月, 2020 2 次提交
  3. 18 11月, 2020 3 次提交
  4. 15 11月, 2020 1 次提交
    • J
      io_uring: handle -EOPNOTSUPP on path resolution · 944d1444
      Jens Axboe 提交于
      Any attempt to do path resolution on /proc/self from an async worker will
      yield -EOPNOTSUPP. We can safely do that resolution from the task itself,
      and without blocking, so retry it from there.
      
      Ideally io_uring would know this upfront and not have to go through the
      worker thread to find out, but that doesn't currently seem feasible.
      Signed-off-by: NJens Axboe <axboe@kernel.dk>
      944d1444
  5. 12 11月, 2020 1 次提交
    • J
      io_uring: round-up cq size before comparing with rounded sq size · 88ec3211
      Jens Axboe 提交于
      If an application specifies IORING_SETUP_CQSIZE to set the CQ ring size
      to a specific size, we ensure that the CQ size is at least that of the
      SQ ring size. But in doing so, we compare the already rounded up to power
      of two SQ size to the as-of yet unrounded CQ size. This means that if an
      application passes in non power of two sizes, we can return -EINVAL when
      the final value would've been fine. As an example, an application passing
      in 100/100 for sq/cq size should end up with 128 for both. But since we
      round the SQ size first, we compare the CQ size of 100 to 128, and return
      -EINVAL as that is too small.
      
      Cc: stable@vger.kernel.org
      Fixes: 33a107f0 ("io_uring: allow application controlled CQ ring size")
      Reported-by: NDan Melnic <dmm@fb.com>
      Signed-off-by: NJens Axboe <axboe@kernel.dk>
      88ec3211
  6. 11 11月, 2020 1 次提交
  7. 06 11月, 2020 3 次提交
  8. 05 11月, 2020 1 次提交