All of lore.kernel.org
 help / color / mirror / Atom feed
From: Victor Stewart <v@nametag.social>
To: io-uring <io-uring@vger.kernel.org>
Subject: [BUG? liburing] io_uring_register_files_update with liburing 2.0 on 5.13.17
Date: Sat, 18 Sep 2021 14:41:05 +0100	[thread overview]
Message-ID: <CAM1kxwjCjo9u5AwAn0UANCWkahkUYz8PwHkWgF0U83ue=KbfTA@mail.gmail.com> (raw)

just auto updated from 5.13.16 to 5.13.17, and suddenly my fixed
file registrations fail with EOPNOTSUPP using liburing 2.0.

static inline struct io_uring ring;
static inline int *socketfds;

// ...

void enableFD(int fd)
{
   int result = io_uring_register_files_update(&ring, fd,
                      &(socketfds[fd] = fd), 1);
   printf("enableFD, result = %d\n", result);
}

maybe this is due to the below and related work that
occurred at the end of 5.13 and liburing got out of sync?

https://github.com/torvalds/linux/commit/992da01aa932b432ef8dc3885fa76415b5dbe43f#diff-79ffab63f24ef28eec3badbc8769e2a23e0475ab1fbe390207269ece944a0824

and can't use liburing 2.1 because of the api changes since 5.13.

             reply	other threads:[~2021-09-18 13:41 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-18 13:41 Victor Stewart [this message]
2021-09-18 14:41 ` [BUG? liburing] io_uring_register_files_update with liburing 2.0 on 5.13.17 Jens Axboe
2021-09-18 20:13   ` Victor Stewart
2021-09-18 20:26     ` Jens Axboe
2021-09-18 20:38       ` Jens Axboe
2021-09-18 21:55         ` Victor Stewart
2021-09-18 22:21           ` Jens Axboe
2021-09-18 23:19             ` Victor Stewart
2021-09-18 23:23               ` Victor Stewart
2021-09-18 23:37               ` Jens Axboe
2021-09-18 23:40                 ` Jens Axboe
2021-09-19  4:15                   ` Vito Caputo
2021-09-19 14:16                     ` Jens Axboe
2021-09-20 12:51                   ` Victor Stewart
2021-09-20 13:10                     ` Jens Axboe
2021-09-20 13:19                       ` Victor Stewart
2021-09-19 11:56             ` Pavel Begunkov
2021-09-19 14:24               ` 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='CAM1kxwjCjo9u5AwAn0UANCWkahkUYz8PwHkWgF0U83ue=KbfTA@mail.gmail.com' \
    --to=v@nametag.social \
    --cc=io-uring@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.