From: Christoph Hellwig <hch@infradead.org>
To: Liang Chen <liangchen.linux@gmail.com>
Cc: Christoph Hellwig <hch@infradead.org>,
linux-bcache@vger.kernel.org, linux-kernel@vger.kernel.org,
colyli@suse.de, bcache@linux.ewheeler.net
Subject: Re: [PATCH] bcache: avoid a dangerous addressing in closure_queue
Date: Wed, 5 Jul 2017 20:36:28 -0700 [thread overview]
Message-ID: <20170706033628.GA1007@infradead.org> (raw)
In-Reply-To: <CAKhg4tLchH_+sR7VXq=hR7tHU_NRsrsxk6PVTfYx1-B5pA0W+w@mail.gmail.com>
On Thu, Jul 06, 2017 at 08:18:02AM +0800, Liang Chen wrote:
> But as you pointed out, explicit casting is still bad too (was hoping it can be
> considered less bad at this situation). I will think of a better idea
> to handle this
> issue unless people agree that the current behaviour is safe.
Yes, let's find a way to avoids both the implicit and the explicit cast.
prev parent reply other threads:[~2017-07-06 3:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-05 12:53 [PATCH] bcache: avoid a dangerous addressing in closure_queue Liang Chen
2017-07-05 19:31 ` Christoph Hellwig
2017-07-06 0:18 ` Liang Chen
2017-07-06 3:36 ` 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=20170706033628.GA1007@infradead.org \
--to=hch@infradead.org \
--cc=bcache@linux.ewheeler.net \
--cc=colyli@suse.de \
--cc=liangchen.linux@gmail.com \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.