public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@amd64.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Denis Kirjanov <kirjanov@gmail.com>,
	linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH] edac: fix buffer overrun if no suitable bandwidth found
Date: Tue, 23 Oct 2012 23:38:45 +0200	[thread overview]
Message-ID: <20121023213845.GA21115@aftab.osrc.amd.com> (raw)
In-Reply-To: <20121023140939.28ed0df4.akpm@linux-foundation.org>

On Tue, Oct 23, 2012 at 02:09:39PM -0700, Andrew Morton wrote:
> On Tue, 23 Oct 2012 22:49:26 +0200
> Borislav Petkov <bp@amd64.org> wrote:
> 
> > Now you only need to give me a proper patch with your S-O-B and we're
> > ready to go :).
> 
> who, me, what?!?!  Sounds stressful.

Yeah, this is to show you how we all feel when we're on the sending end
of patches :-).

> 
> umm, OK here we go.
> 
> What I don't understand is the effects of the bug.  If the present code
> can indeed start using the n+1th element of the array then it's writing
> random garbage into the hardware.  If this can ever happen then I
> suspect that yes, a cc:stable is needed?

Yes, cc:stable is needed.

The code has a very subtle bug because I should've robustified it from
the get-go instead of fiddling with it.

Basically, this is what happens:

If you supply new_bw < 761, i.e. so that the last element matches, *and*
you have a minimum scrubrate set to != 0x0 (due to unsupported scrubrate
settings on some families) the first continue in the loop with i being
22 (last array element) terminates the loop after incrementing i one
last time.

Thus, it doesn't let us break out of it in the next statement where
the new_bw will match and we'll be able to exit the loop without it
incrementing i one last time and thus get us out of bounds.

So yes, your fix is correct, I'll test it tomorrow just in case and
will sit down and rewrite this loop because it pisses me off to see how
stupidly fragile it is.

And I see you'll carry this patch so I won't send it to Linus next merge
window so thanks for this!

> From: Andrew Morton <akpm@linux-foundation.org>
> Subject: drivers/edac/amd64_edac.c:__amd64_set_scrub_rate(): avoid overindexing scrubrates[]
> 
> If none of the elements in scrubrates[] matches, this loop will cause
> __amd64_set_scrub_rate() to incorrectly use the n+1th element.
> 
> As the function is designed to use the final scrubrates[] element in the
> case of no match, we can fix this bug by simply terminating the array
> search at the n-1th element.
> 
> Reported-by: Denis Kirjanov <kirjanov@gmail.com>
> Cc: Doug Thompson <dougthompson@xmission.com>
> Cc: Borislav Petkov <borislav.petkov@amd.com>

Acked-by: Borislav Petkov <borislav.petkov@amd.com>
Cc: stable@vger.kernel.org

> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>

[ … ]

-- 
Regards/Gruss,
Boris.

Advanced Micro Devices GmbH
Einsteinring 24, 85609 Dornach
GM: Alberto Bozzo
Reg: Dornach, Landkreis Muenchen
HRB Nr. 43632 WEEE Registernr: 129 19551

  reply	other threads:[~2012-10-23 21:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-22 15:30 [PATCH] edac: fix buffer overrun if no suitable bandwidth found Denis Kirjanov
2012-10-23 15:39 ` Borislav Petkov
2012-10-23 19:10 ` Andrew Morton
2012-10-23 20:26   ` Borislav Petkov
2012-10-23 20:37     ` Andrew Morton
2012-10-23 20:49       ` Borislav Petkov
2012-10-23 21:09         ` Andrew Morton
2012-10-23 21:38           ` Borislav Petkov [this message]
2012-10-23 21:58             ` Andrew Morton

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=20121023213845.GA21115@aftab.osrc.amd.com \
    --to=bp@amd64.org \
    --cc=akpm@linux-foundation.org \
    --cc=kirjanov@gmail.com \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@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