linux-kernel - Re: [PATCH] bcache: avoid a dangerous addressing in closure

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20170706033628.GA1007@infradead.org>
Date:   Wed, 5 Jul 2017 20:36:28 -0700
From:   Christoph Hellwig <hch@...radead.org>
To:     Liang Chen <liangchen.linux@...il.com>
Cc:     Christoph Hellwig <hch@...radead.org>,
        linux-bcache@...r.kernel.org, linux-kernel@...r.kernel.org,
        colyli@...e.de, bcache@...ux.ewheeler.net
Subject: Re: [PATCH] bcache: avoid a dangerous addressing in closure_queue

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.