From: "Guilherme G. Piccoli" <gpiccoli@canonical.com>
To: Song Liu <liu.song.a23@gmail.com>
Cc: linux-block@vger.kernel.org,
linux-raid <linux-raid@vger.kernel.org>,
dm-devel@redhat.com, axboe@kernel.dk,
Gavin Guo <gavin.guo@canonical.com>,
Jay Vosburgh <jay.vosburgh@canonical.com>,
"Guilherme G. Piccoli" <kernel@gpiccoli.net>,
stable@vger.kernel.org, Bart Van Assche <bvanassche@acm.org>,
Ming Lei <ming.lei@redhat.com>, Eric Ren <renzhengeek@gmail.com>,
hch@infradead.org
Subject: Re: [PATCH V2 1/2] block: Fix a NULL pointer dereference in generic_make_request()
Date: Thu, 23 May 2019 11:33:21 -0300 [thread overview]
Message-ID: <3e583b2d-742a-3238-69ed-7a2e6cce417b@canonical.com> (raw)
In-Reply-To: <CAPhsuW6KayaNR-0eFHpvPG-LVuPFL_1OFjvZpOcnapVFe2vC9Q@mail.gmail.com>
On 21/05/2019 02:59, Song Liu wrote:
>
> Applied both patches! Thanks for the fix!
Hi Song, sorry for the annoyance, but the situation of both patches is a
bit confused for me heheh
You mention you've applied both patches - I couldn't find your tree.
Also, Christoph noticed Ming's series fixes both issues and suggested to
drop both my patches in favor of Ming's clean-up, or at least make them
-stable only.
So, what is the current status of the patches? Can we have them on
-stable trees at least? If so, how should I proceed?
Thanks in advance for the clarification!
Cheers,
Guilherme
next prev parent reply other threads:[~2019-05-23 14:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-20 22:09 [PATCH V2 1/2] block: Fix a NULL pointer dereference in generic_make_request() Guilherme G. Piccoli
2019-05-20 22:09 ` [PATCH V2 2/2] md/raid0: Do not bypass blocking queue entered for raid0 bios Guilherme G. Piccoli
2019-05-21 12:56 ` Christoph Hellwig
2019-05-21 14:10 ` Guilherme Piccoli
2019-05-21 17:22 ` Christoph Hellwig
2019-05-21 17:37 ` Guilherme Piccoli
2019-05-21 5:59 ` [PATCH V2 1/2] block: Fix a NULL pointer dereference in generic_make_request() Song Liu
2019-05-21 12:07 ` Guilherme Piccoli
2019-05-23 14:33 ` Guilherme G. Piccoli [this message]
2019-05-23 17:06 ` Song Liu
2019-05-23 20:30 ` Guilherme Piccoli
2019-05-21 12:51 ` Christoph Hellwig
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=3e583b2d-742a-3238-69ed-7a2e6cce417b@canonical.com \
--to=gpiccoli@canonical.com \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=dm-devel@redhat.com \
--cc=gavin.guo@canonical.com \
--cc=hch@infradead.org \
--cc=jay.vosburgh@canonical.com \
--cc=kernel@gpiccoli.net \
--cc=linux-block@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=liu.song.a23@gmail.com \
--cc=ming.lei@redhat.com \
--cc=renzhengeek@gmail.com \
--cc=stable@vger.kernel.org \
/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).