From: Dylan Yudaken <[email protected]>
To: Dylan Yudaken <[email protected]>,
"[email protected]" <[email protected]>,
"[email protected]" <[email protected]>,
"[email protected]" <[email protected]>
Cc: Kernel Team <[email protected]>,
"[email protected]" <[email protected]>
Subject: Re: [PATCH liburing] test that unregister_files processes task work
Date: Mon, 7 Nov 2022 13:37:13 +0000 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On Mon, 2022-11-07 at 20:04 +0700, Ammar Faizi wrote:
> On 11/7/22 7:35 PM, Dylan Yudaken wrote:
> > +static int test_defer_taskrun(void)
> > +{
> > + struct io_uring_sqe *sqe;
> > + struct io_uring ring;
> > + int ret, fds[2];
> > + char buff = 'x';
> > +
> > + ret = io_uring_queue_init(8, &ring,
> > + IORING_SETUP_DEFER_TASKRUN |
> > IORING_SETUP_SINGLE_ISSUER);
> > + if (ret)
> > + return T_EXIT_SKIP;
>
> You return T_EXIT_SKIP from test_defer_taskrun(). But the
> call site is:
>
> > + if (t_probe_defer_taskrun()) {
> > + ret = test_defer_taskrun();
> > + if (ret) {
> > + fprintf(stderr, "test_defer failed\n");
> > + return T_EXIT_FAIL;
> > + }
> > + }
>
> T_EXIT_SKIP is 77. So the block inside the "if" is taken.
> End result you get T_EXIT_FAIL.
>
> T_EXIT_SKIP in your code doesn't really mean skip.
>
Ah yes - I added the probe and then forgot to take out the skip.
Thanks for spotting.
Dylan
prev parent reply other threads:[~2022-11-07 13:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-07 12:35 [PATCH liburing] test that unregister_files processes task work Dylan Yudaken
2022-11-07 13:04 ` Ammar Faizi
2022-11-07 13:37 ` Dylan Yudaken [this message]
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=b0ce80cf1aa966bcdff46fbbc008b97249e25111.camel@fb.com \
[email protected] \
[email protected] \
[email protected] \
[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