io-uring.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Xiaoguang Wang <xiaoguang.wang@linux.alibaba.com>
To: Jens Axboe <axboe@kernel.dk>, io-uring@vger.kernel.org
Cc: asml.silence@gmail.com
Subject: Re: [PATCH] io_uring: add missing sigmask restore in io_cqring_wait()
Date: Tue, 14 Sep 2021 22:28:33 +0800	[thread overview]
Message-ID: <f0c26fd2-667f-8f94-446d-4da064a712d9@linux.alibaba.com> (raw)
In-Reply-To: <45cb9bb5-3132-6873-a423-d037e6db01a5@kernel.dk>

hi,


> On 9/14/21 2:41 AM, Xiaoguang Wang wrote:
>> Found this by learning codes.
> Does look like a real bug. But how about we move the get_timespec() section
> before the sigmask saving?

Ok,  I thought about this method before :)


Regards,

Xiaoguang Wang

>

  reply	other threads:[~2021-09-14 14:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-14  8:41 [PATCH] io_uring: add missing sigmask restore in io_cqring_wait() Xiaoguang Wang
2021-09-14 13:42 ` Jens Axboe
2021-09-14 14:28   ` Xiaoguang Wang [this message]
2021-09-14 14:29     ` 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=f0c26fd2-667f-8f94-446d-4da064a712d9@linux.alibaba.com \
    --to=xiaoguang.wang@linux.alibaba.com \
    --cc=asml.silence@gmail.com \
    --cc=axboe@kernel.dk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).