From: Jens Axboe <axboe@kernel.dk>
To: Hillf Danton <hdanton@sina.com>
Cc: Pavel Begunkov <asml.silence@gmail.com>,
io-uring@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
viro@zeniv.linux.org.uk,
syzbot+107dd59d1efcaf3ffca4@syzkaller.appspotmail.com,
Stefano Garzarella <sgarzare@redhat.com>,
Kees Cook <keescook@chromium.org>
Subject: Re: [PATCH next] io_uring: fix task hung in io_uring_setup
Date: Tue, 8 Sep 2020 17:34:26 -0600 [thread overview]
Message-ID: <c7a4b985-6f22-96b7-d84c-cf3c91ddf79c@kernel.dk> (raw)
In-Reply-To: <20200908000339.2260-1-hdanton@sina.com>
On 9/7/20 6:03 PM, Hillf Danton wrote:
>
> On Mon, 7 Sep 2020 06:55:04 Jens Axboe wrote:
>> On 9/7/20 2:50 AM, Pavel Begunkov wrote:
>>>
>>> BTW, I don't see the patch itself, and it's neither in io_uring, block
>>> nor fs mailing lists. Hillf, could you please CC proper lists next time?
>
> Yes, I can. So will I send io_uring patches with Pavel Cced.
While that is nice, it should not be necessary. We need to ensure that your
emails reach the list, that's more important than needing to CC a specific
person, because it still means that everyone else doesn't see it.
Do you get an error from vger, or does it simply not show up?
--
Jens Axboe
next prev parent reply other threads:[~2020-09-08 23:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200903132119.14564-1-hdanton@sina.com>
2020-09-03 14:04 ` [PATCH next] io_uring: fix task hung in io_uring_setup Jens Axboe
2020-09-07 8:50 ` Pavel Begunkov
2020-09-07 12:55 ` Jens Axboe
[not found] ` <20200908000339.2260-1-hdanton@sina.com>
2020-09-08 20:58 ` Pavel Begunkov
2020-09-08 23:34 ` Jens Axboe [this message]
[not found] ` <20200909001943.18916-1-hdanton@sina.com>
2020-09-09 14:24 ` Jens Axboe
2020-09-07 8:43 ` Stefano Garzarella
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=c7a4b985-6f22-96b7-d84c-cf3c91ddf79c@kernel.dk \
--to=axboe@kernel.dk \
--cc=asml.silence@gmail.com \
--cc=hdanton@sina.com \
--cc=io-uring@vger.kernel.org \
--cc=keescook@chromium.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sgarzare@redhat.com \
--cc=syzbot+107dd59d1efcaf3ffca4@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
/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).