From: Dominique Martinet <asmadeus@codewreck.org>
To: Tomas Bortoli <tomasbortoli@gmail.com>
Cc: Dominique Martinet <dominique.martinet@cea.fr>,
v9fs-developer@lists.sourceforge.net,
netdev <netdev@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Eric Van Hensbergen <ericvh@gmail.com>,
Latchesar Ionkov <lucho@ionkov.net>
Subject: Re: [PATCH 2/2] 9p/trans_fd: put worker reqs on destroy
Date: Mon, 15 Oct 2018 12:46:36 +0200 [thread overview]
Message-ID: <20181015104636.GA14200@nautica> (raw)
In-Reply-To: <CAAHj5qgBteZQOkjF-n3OXvN9e0v6NYEsqg3YOitEKW0jikTpng@mail.gmail.com>
Tomas Bortoli wrote on Tue, Oct 09, 2018:
> Il giorno mar 9 ott 2018 alle ore 06:06 Dominique Martinet
> > Fixes: 728356dedeff8 ("9p: Add refcount to p9_req_t")
> > Signed-off-by: Dominique Martinet <dominique.martinet@cea.fr>
> > Cc: Eric Van Hensbergen <ericvh@gmail.com>
> > Cc: Latchesar Ionkov <lucho@ionkov.net>
> > Cc: Tomas Bortoli <tomasbortoli@gmail.com>
>
> Reviewed-by: Tomas Bortoli <tomasbortoli@gmail.com>
Thanks Tomas.
Tests seem ok, I've push both patches to my next branch, and will submit
them with the rest in a couple of weeks.
Quite a few of my patches haven't had reviews this cycle, if you read
this and have a bit of time, please pull my branch and have a read, or
each commit has a link to the lkml post to reply somewhat easily.
Reminder gir url:
git://github.com/martinetd/linux 9p-next
--
Dominique
next prev parent reply other threads:[~2018-10-15 10:46 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-16 5:59 BUG: corrupted list in p9_read_work syzbot
2018-10-09 1:07 ` syzbot
2018-10-09 2:09 ` Dominique Martinet
2018-10-09 4:05 ` [PATCH 1/2] 9p/trans_fd: abort p9_read_work if req status changed Dominique Martinet
2018-10-09 4:05 ` [PATCH 2/2] 9p/trans_fd: put worker reqs on destroy Dominique Martinet
2018-10-09 13:19 ` Tomas Bortoli
2018-10-15 10:46 ` Dominique Martinet [this message]
2018-10-10 14:03 ` BUG: corrupted list in p9_read_work Dmitry Vyukov
2018-10-10 14:40 ` Dominique Martinet
2018-10-10 14:51 ` Dmitry Vyukov
2018-10-10 15:58 ` Dominique Martinet
2018-10-11 12:33 ` Dmitry Vyukov
2018-10-11 13:10 ` Dominique Martinet
2018-10-11 13:27 ` Dmitry Vyukov
2018-10-11 13:40 ` Dmitry Vyukov
2018-10-11 14:28 ` 9p/RDMA for syzkaller (Was: BUG: corrupted list in p9_read_work) Dominique Martinet
2018-10-12 14:42 ` Dmitry Vyukov
2018-10-11 14:19 ` Dominique Martinet
2018-10-12 14:50 ` Dmitry Vyukov
2018-10-12 15:08 ` Dominique Martinet
2018-11-17 8:46 ` Dominique Martinet
2018-11-20 11:20 ` Dmitry Vyukov
2018-11-20 11:28 ` Dominique Martinet
2018-10-10 14:29 ` BUG: corrupted list in p9_read_work Dmitry Vyukov
2018-10-10 14:48 ` Dominique Martinet
2018-10-10 14:49 ` syzbot
2018-10-10 16:00 ` Dominique Martinet
2018-10-10 16:02 ` syzbot
2018-10-10 16:10 ` Dominique Martinet
2018-10-10 16:29 ` syzbot
2018-10-10 16:36 ` Dmitry Vyukov
2018-10-10 22:55 ` Dominique Martinet
2018-10-10 14:42 ` Dmitry Vyukov
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=20181015104636.GA14200@nautica \
--to=asmadeus@codewreck.org \
--cc=dominique.martinet@cea.fr \
--cc=ericvh@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lucho@ionkov.net \
--cc=netdev@vger.kernel.org \
--cc=tomasbortoli@gmail.com \
--cc=v9fs-developer@lists.sourceforge.net \
/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).