From: Christoph Hellwig <hch@lst.de>
To: Shaohua Li <shli@fb.com>
Cc: neilb@suse.de, dan.j.williams@intel.com,
linux-raid@vger.kernel.org, Kernel-team@fb.com,
Song Liu <songliubraving@fb.com>
Subject: Re: fix use after free in raid5-cache
Date: Wed, 2 Sep 2015 19:22:55 +0200 [thread overview]
Message-ID: <20150902172255.GA25723@lst.de> (raw)
In-Reply-To: <20150902165522.GA2792971@devbig257.prn2.facebook.com>
Ok, I spotted the break there now. Feel free to rebase it and please
push your current tree out, as I have a bunch of other changes pending.
prev parent reply other threads:[~2015-09-02 17:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-02 14:14 fix use after free in raid5-cache Christoph Hellwig
2015-09-02 14:14 ` [PATCH 1/3] raid5-cache: move functionality out of __r5l_set_io_unit_state Christoph Hellwig
2015-09-02 14:14 ` [PATCH 2/3] raid5-cache: remove r5l_move_io_unit_list Christoph Hellwig
2015-09-02 14:14 ` [PATCH 3/3] raid5-cache: fix __r5l_stripe_write_finished Christoph Hellwig
2015-09-02 16:55 ` fix use after free in raid5-cache Shaohua Li
2015-09-02 17:22 ` Christoph Hellwig [this message]
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=20150902172255.GA25723@lst.de \
--to=hch@lst.de \
--cc=Kernel-team@fb.com \
--cc=dan.j.williams@intel.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
--cc=shli@fb.com \
--cc=songliubraving@fb.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;
as well as URLs for NNTP newsgroup(s).