From: Markus Elfring <Markus.Elfring@web.de>
To: Luis Chamberlain <mcgrof@kernel.org>,
linux-block@vger.kernel.org, linux-fsdevel@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
syzbot+603294af2d01acfdd6da@syzkaller.appspotmail.com,
Al Viro <viro@zeniv.linux.org.uk>,
Andrew Morton <akpm@linux-foundation.org>,
Bart Van Assche <bvanassche@acm.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Hannes Reinecke <hare@suse.com>, Ingo Molnar <mingo@redhat.com>,
Jan Kara <jack@suse.cz>, Jens Axboe <axboe@kernel.dk>,
Michal Hocko <mhocko@kernel.org>, Michal Hocko <mhocko@suse.com>,
Ming Lei <ming.lei@redhat.com>, Nicolai Stange <nstange@suse.de>,
Omar Sandoval <osandov@fb.com>,
Steven Rostedt <rostedt@goodmis.org>,
Yu Kuai <yukuai3@huawei.com>
Subject: Re: [PATCH v3 4/6] blktrace: fix debugfs use after free
Date: Wed, 29 Apr 2020 10:48:21 +0200 [thread overview]
Message-ID: <78375104-16a5-ea1d-f894-b09b1224d189@web.de> (raw)
> …, but a misuse of debugfs within blktace.
How do you think about to avoid a typo here for the final change description?
Regards,
Markus
next reply other threads:[~2020-04-29 8:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-29 8:48 Markus Elfring [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-04-29 7:46 [PATCH v3 0/6] block: fix blktrace " Luis Chamberlain
2020-04-29 7:46 ` [PATCH v3 4/6] blktrace: fix " Luis Chamberlain
2020-04-29 9:47 ` Greg KH
2020-04-29 11:26 ` Christoph Hellwig
2020-04-29 11:45 ` Luis Chamberlain
2020-04-29 11:50 ` Christoph Hellwig
2020-04-29 12:02 ` Luis Chamberlain
2020-04-29 12:04 ` Christoph Hellwig
2020-04-29 12:21 ` Luis Chamberlain
2020-04-29 12:57 ` Greg KH
2020-05-01 15:24 ` Luis Chamberlain
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=78375104-16a5-ea1d-f894-b09b1224d189@web.de \
--to=markus.elfring@web.de \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=gregkh@linuxfoundation.org \
--cc=hare@suse.com \
--cc=jack@suse.cz \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mcgrof@kernel.org \
--cc=mhocko@kernel.org \
--cc=mhocko@suse.com \
--cc=ming.lei@redhat.com \
--cc=mingo@redhat.com \
--cc=nstange@suse.de \
--cc=osandov@fb.com \
--cc=rostedt@goodmis.org \
--cc=syzbot+603294af2d01acfdd6da@syzkaller.appspotmail.com \
--cc=viro@zeniv.linux.org.uk \
--cc=yukuai3@huawei.com \
/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