public inbox for [email protected]
 help / color / mirror / Atom feed
From: Bijan Mottahedeh <[email protected]>
To: [email protected]
Cc: [email protected]
Subject: [PATCH 0/1] io_uring: validate the full range of provided buffers for access
Date: Thu,  4 Jun 2020 18:01:51 -0700	[thread overview]
Message-ID: <[email protected]> (raw)

I hard coded (user_max_address() - PAGESIZE) as the start address 
in liburing/test/read-write.c:test_buf_select() and provided two buffers
of PAGESIZE each.  Without the patch, io_uring_prep_provide_buffers()
succeeds but the subsequent __test_io() obviously fails with -EFAULT.
With the patch, io_uring_prep_provide_buffers() fails with -EFAULT.
I think this would be a good test case to add but I'm not sure what
would be a generic way to implement it.

Bijan Mottahedeh (1):
  io_uring: validate the full range of provided buffers for access

 fs/io_uring.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

-- 
1.8.3.1


             reply	other threads:[~2020-06-05  1:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-05  1:01 Bijan Mottahedeh [this message]
2020-06-05  1:01 ` [PATCH 1/1] io_uring: validate the full range of provided buffers for access Bijan Mottahedeh
2020-06-05  1:33 ` [PATCH 0/1] " Jens Axboe

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1591318912-34736-1-git-send-email-bijan.mottahedeh@oracle.com \
    [email protected] \
    [email protected] \
    [email protected] \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox