linux-bcache.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Liang Chen <liangchen.linux@gmail.com>
To: linux-bcache@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, colyli@suse.de,
	bcache@linux.ewheeler.net, Liang Chen <liangchen.linux@gmail.com>
Subject: [PATCH] bcache: avoid a dangerous addressing in closure_queue
Date: Wed,  5 Jul 2017 20:53:19 +0800	[thread overview]
Message-ID: <1499259199-15161-1-git-send-email-liangchen.linux@gmail.com> (raw)

The use of the union reduces the size of closure struct by taking advantage
of the current size of its members. The offset of func in work_struct equals
the size of the first three members, so that work.work_func will just
reference the forth member - the pointer to closure_fn.

This is smart but dangerous. It can be broken if work_struct or the other
ones get changed, and can be a bit difficult to debug.

Signed-off-by: Liang Chen <liangchen.linux@gmail.com>
---
 drivers/md/bcache/closure.h | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/drivers/md/bcache/closure.h b/drivers/md/bcache/closure.h
index 1ec84ca..665c470 100644
--- a/drivers/md/bcache/closure.h
+++ b/drivers/md/bcache/closure.h
@@ -251,8 +251,9 @@ static inline void set_closure_fn(struct closure *cl, closure_fn *fn,
 static inline void closure_queue(struct closure *cl)
 {
 	struct workqueue_struct *wq = cl->wq;
+	closure_fn		*fn = cl->fn;
 	if (wq) {
-		INIT_WORK(&cl->work, cl->work.func);
+		INIT_WORK(&cl->work, (work_func_t)fn);
 		BUG_ON(!queue_work(wq, &cl->work));
 	} else
 		cl->fn(cl);
-- 
1.8.3.1

             reply	other threads:[~2017-07-05 12:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-05 12:53 Liang Chen [this message]
2017-07-05 19:31 ` [PATCH] bcache: avoid a dangerous addressing in closure_queue Christoph Hellwig
2017-07-06  0:18   ` Liang Chen
2017-07-06  3:36     ` 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=1499259199-15161-1-git-send-email-liangchen.linux@gmail.com \
    --to=liangchen.linux@gmail.com \
    --cc=bcache@linux.ewheeler.net \
    --cc=colyli@suse.de \
    --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 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).