Linux-Fsdevel Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Pavel Begunkov <asml.silence@gmail.com>
To: Hillf Danton <hdanton@sina.com>, Jens Axboe <axboe@kernel.dk>
Cc: 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 23:58:39 +0300	[thread overview]
Message-ID: <778a8166-e031-e691-a44b-1199c68d6a29@gmail.com> (raw)
In-Reply-To: <20200908000339.2260-1-hdanton@sina.com>

On 08/09/2020 03:03, 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.

Thanks

>>
>> He did, but I'm guessing that vger didn't like the email for whatever
>> reason. Hillf, did you get an error back from vger when sending the pat	
> 
> My inbox, a simple free mail, is perhaps blocked as spam at the vger end.

-- 
Pavel Begunkov

  parent reply	other threads:[~2020-09-08 21:01 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 ` 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 [this message]
2020-09-08 23:34       ` Jens Axboe
     [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=778a8166-e031-e691-a44b-1199c68d6a29@gmail.com \
    --to=asml.silence@gmail.com \
    --cc=axboe@kernel.dk \
    --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 \
    --subject='Re: [PATCH next] io_uring: fix task hung in io_uring_setup' \
    /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

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).