From: "Luck, Tony" <tony.luck@intel.com>
To: James Morse <james.morse@arm.com>
Cc: Eiichi Tsukata <devel@etsukata.com>,
bp@alien8.de, mchehab@kernel.org, linux-edac@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] EDAC: Fix global-out-of-bounds write when setting edac_mc_poll_msec
Date: Thu, 27 Jun 2019 10:36:49 -0700 [thread overview]
Message-ID: <20190627173649.GA18346@agluck-desk2.amr.corp.intel.com> (raw)
In-Reply-To: <ee91dd9d-e9ac-4fee-d7f2-152195995ecb@arm.com>
On Thu, Jun 27, 2019 at 06:11:18PM +0100, James Morse wrote:
> Hello,
>
> (CC: +Tony Luck.
> Original Patch: lore.kernel.org/r/20190626054011.30044-1-devel@etsukata.com )
Heh: My mail agent "helpfully" made that clickable, but as a "mailto:"
URL rather than an https: one!
>
> On 26/06/2019 06:40, Eiichi Tsukata wrote:
> > Commit 9da21b1509d8 ("EDAC: Poll timeout cannot be zero, p2") assumes
> > edac_mc_poll_msec to be unsigned long, but the type of the variable still
> > remained as int. Setting edac_mc_poll_msec can trigger out-of-bounds
> > write.
>
> Thanks for catching this!
Ditto & likewise.
>
>
> > Fix it by changing the type of edac_mc_poll_msec to unsigned int.
>
> This means reverting more of 9da21b1509d8, but it also fixes signed/unsigned issues:
> | root@debian-guest:/sys/module/edac_core/parameters# echo 4294967295 > edac_mc_poll_msec
> | root@debian-guest:/sys/module/edac_core/parameters# cat edac_mc_poll_msec
> | -1
> | root@debian-guest:/sys/module/edac_core/parameters# echo -1 > edac_mc_poll_msec
> | -bash: echo: write error: Invalid argument
>
>
> > The reason why this patch adopts unsigned int rather than unsigned long
> > is msecs_to_jiffies() assumes arg to be unsigned int.
>
> Ah, so the range is limited anyway.
>
> It looks like it was switched to long to be consistent with edac_mc_workq_setup(), which
> has since been removed in preference to msecs_to_jiffies().
>
>
> Reviewed-by: James Morse <james.morse@arm.com>
Applied. (Boris left me in charge of EDAC bits for the
next few weeks). It will show up in the for_5.3 branch
of:
git://git.kernel.org/pub/scm/linux/kernel/git/ras/ras.git
after test builds complete.
-Tony
prev parent reply other threads:[~2019-06-27 17:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-26 5:40 Eiichi Tsukata
2019-06-27 17:11 ` James Morse
2019-06-27 17:36 ` Luck, Tony [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=20190627173649.GA18346@agluck-desk2.amr.corp.intel.com \
--to=tony.luck@intel.com \
--cc=bp@alien8.de \
--cc=devel@etsukata.com \
--cc=james.morse@arm.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@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
all inboxes | Powered by JetHome®