All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: shli@kernel.org
Cc: linux-raid@vger.kernel.org
Subject: re: raid5: offload stripe handle to workqueue
Date: Tue, 15 Jul 2014 18:49:45 +0300	[thread overview]
Message-ID: <20140715154945.GA29698@mwanda> (raw)

Hello Shaohua Li,

The patch 851c30c9badf: "raid5: offload stripe handle to workqueue"
from Aug 28, 2013, leads to the following static checker warning:

	drivers/md/raid5.c:5554 alloc_thread_groups()
	warn: integer overflows in allocation

drivers/md/raid5.c
  5537  static int alloc_thread_groups(struct r5conf *conf, int cnt,
                                                            ^^^^^^^
"cnt" comes from the user as an unsigned long in
raid5_store_group_thread_cnt() but we truncate it to int here.  It would
be cleaner if the types were the same through out.

  5538                                 int *group_cnt,
  5539                                 int *worker_cnt_per_group,
  5540                                 struct r5worker_group **worker_groups)
  5541  {
  5542          int i, j, k;
  5543          ssize_t size;
  5544          struct r5worker *workers;
  5545  
  5546          *worker_cnt_per_group = cnt;
  5547          if (cnt == 0) {
  5548                  *group_cnt = 0;
  5549                  *worker_groups = NULL;
  5550                  return 0;
  5551          }
  5552          *group_cnt = num_possible_nodes();
  5553          size = sizeof(struct r5worker) * cnt;
                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Integer overflow #1.

  5554          workers = kzalloc(size * *group_cnt, GFP_NOIO);
                                  ^^^^^^^^^^^^^^^^^
Integer overflow #2.

  5555          *worker_groups = kzalloc(sizeof(struct r5worker_group) *
  5556                                  *group_cnt, GFP_NOIO);


TODO-list: 2014-07-14: raid5: integer overflows in alloc_thread_groups()

regards,
dan carpenter

                 reply	other threads:[~2014-07-15 15:49 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20140715154945.GA29698@mwanda \
    --to=dan.carpenter@oracle.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=shli@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.