Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1681966

Re: [PATCH] bcache: avoid a dangerous addressing in closure_queue

From Liang Chen <liangchen.linux@gmail.com>
Newsgroups linux.kernel
Subject Re: [PATCH] bcache: avoid a dangerous addressing in closure_queue
Date 2017-07-06 02:20 +0200
Message-ID <u02Gt-59t-5@gated-at.bofh.it> (permalink)
References <tZS4p-6k6-1@gated-at.bofh.it> <tZYjw-2dl-9@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


I had the same feeling, and was reluctant to do so. The reason for making this
change was that current code implicitly converts work_func_t to closure_fn, and
it also depends on the offset and size of a few struct not being changed. So the
patch was introduced essentially to solve that, and keep the impact small
meanwhile.

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.

Back to linux.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

[PATCH] bcache: avoid a dangerous addressing in closure_queue Liang Chen <liangchen.linux@gmail.com> - 2017-07-05 15:00 +0200
  Re: [PATCH] bcache: avoid a dangerous addressing in closure_queue Christoph Hellwig <hch@infradead.org> - 2017-07-05 21:40 +0200
    Re: [PATCH] bcache: avoid a dangerous addressing in closure_queue Liang Chen <liangchen.linux@gmail.com> - 2017-07-06 02:20 +0200
      Re: [PATCH] bcache: avoid a dangerous addressing in closure_queue Christoph Hellwig <hch@infradead.org> - 2017-07-06 05:40 +0200

csiph-web