<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/drivers/edac/amd64_edac.c, branch linux-3.2.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-3.2.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-3.2.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2016-04-30T22:05:14Z</updated>
<entry>
<title>EDAC, amd64_edac: Shift wrapping issue in f1x_get_norm_dct_addr()</title>
<updated>2016-04-30T22:05:14Z</updated>
<author>
<name>Dan Carpenter</name>
</author>
<published>2016-01-20T09:54:51Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=e0d2e02bdbc134227459f0feccc7fa6a14b50966'/>
<id>urn:sha1:e0d2e02bdbc134227459f0feccc7fa6a14b50966</id>
<content type='text'>
commit 6f3508f61c814ee852c199988a62bd954c50dfc1 upstream.

dct_sel_base_off is declared as a u64 but we're only using the lower 32
bits because of a shift wrapping bug. This can possibly truncate the
upper 16 bits of DctSelBaseOffset[47:26], causing us to misdecode the CS
row.

Fixes: c8e518d5673d ('amd64_edac: Sanitize f10_get_base_addr_offset')
Signed-off-by: Dan Carpenter &lt;dan.carpenter@oracle.com&gt;
Cc: Aravind Gopalakrishnan &lt;Aravind.Gopalakrishnan@amd.com&gt;
Cc: linux-edac &lt;linux-edac@vger.kernel.org&gt;
Link: http://lkml.kernel.org/r/20160120095451.GB19898@mwanda
Signed-off-by: Borislav Petkov &lt;bp@suse.de&gt;
Signed-off-by: Ben Hutchings &lt;ben@decadent.org.uk&gt;
</content>
</entry>
<entry>
<title>amd64_edac:__amd64_set_scrub_rate(): avoid overindexing scrubrates[]</title>
<updated>2012-10-30T23:26:55Z</updated>
<author>
<name>Andrew Morton</name>
</author>
<published>2012-10-23T21:09:39Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=1d3bda6f1b995e50f3c8529333471351b986c503'/>
<id>urn:sha1:1d3bda6f1b995e50f3c8529333471351b986c503</id>
<content type='text'>
commit 168bfeef7bba3f9784f7540b053e4ac72b769ce9 upstream.

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.

Boris: this code is fragile anyway, see here why:
http://marc.info/?l=linux-kernel&amp;m=135102834131236&amp;w=2

It will be rewritten more robustly soonish.

Reported-by: Denis Kirjanov &lt;kirjanov@gmail.com&gt;
Cc: Doug Thompson &lt;dougthompson@xmission.com&gt;
Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: Borislav Petkov &lt;borislav.petkov@amd.com&gt;
Signed-off-by: Ben Hutchings &lt;ben@decadent.org.uk&gt;
</content>
</entry>
<entry>
<title>amd64_edac: Cleanup return type of amd64_determine_edac_cap()</title>
<updated>2011-10-06T10:35:46Z</updated>
<author>
<name>Dan Carpenter</name>
</author>
<published>2011-10-06T06:30:25Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=1f6189ed18cbd99d90bffdbc76c3adc54418b2fd'/>
<id>urn:sha1:1f6189ed18cbd99d90bffdbc76c3adc54418b2fd</id>
<content type='text'>
Sparse complains that edac_cap was declared as dev_type and we are
returning edac_type.  Historically, edac_type was correct but since
then we have changed it to return a bit field.

Signed-off-by: Dan Carpenter &lt;dan.carpenter@oracle.com&gt;
Link: http://lkml.kernel.org/r/20111006063025.GA2615@mwanda
Signed-off-by: Borislav Petkov &lt;borislav.petkov@amd.com&gt;
</content>
</entry>
<entry>
<title>amd64_edac: Add a fix for Erratum 505</title>
<updated>2011-10-06T10:34:05Z</updated>
<author>
<name>Borislav Petkov</name>
</author>
<published>2011-09-19T15:34:45Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=73ba85937b2a07b6401ba0b7ca06a112762de9f7'/>
<id>urn:sha1:73ba85937b2a07b6401ba0b7ca06a112762de9f7</id>
<content type='text'>
When accessing the scrub rate control register (F3x58) on F15h, the DRAM
controller selector (F1x10C[DctCfgSel]) has to point to DCT0 so that the
scrub rate configuration can take effect. See Erratum 505 in the AMD
F15h revision guide for more details.

Signed-off-by: Borislav Petkov &lt;borislav.petkov@amd.com&gt;
</content>
</entry>
<entry>
<title>EDAC, MCE, AMD: Simplify NB MCE decoder interface</title>
<updated>2011-10-06T10:34:04Z</updated>
<author>
<name>Borislav Petkov</name>
</author>
<published>2011-08-24T16:44:22Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=b0b07a2bd4fbb6198d4e7142337214eeb77c417a'/>
<id>urn:sha1:b0b07a2bd4fbb6198d4e7142337214eeb77c417a</id>
<content type='text'>
Drop third nbcfg argument which is old remains and not required anymore.

No functionality change.

Signed-off-by: Borislav Petkov &lt;borislav.petkov@amd.com&gt;
</content>
</entry>
<entry>
<title>amd64_edac: Erratum #637 workaround</title>
<updated>2011-04-26T14:18:56Z</updated>
<author>
<name>Borislav Petkov</name>
</author>
<published>2011-03-30T13:42:10Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=c1ae68309b0c1ea67b72e9e94e26b4e819022fc7'/>
<id>urn:sha1:c1ae68309b0c1ea67b72e9e94e26b4e819022fc7</id>
<content type='text'>
F15h CPUs may report a non-DRAM address when reporting an error address
belonging to a CC6 state save area. Add a workaround to detect this
condition and compute the actual DRAM address of the error as documented
in the Revision Guide for AMD Family 15h Models 00h-0Fh Processors.

Signed-off-by: Borislav Petkov &lt;borislav.petkov@amd.com&gt;
</content>
</entry>
<entry>
<title>amd64_edac: Factor in CC6 save area</title>
<updated>2011-04-26T14:18:44Z</updated>
<author>
<name>Borislav Petkov</name>
</author>
<published>2011-03-21T19:45:06Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=f08e457cecece7fbbdad3add9defac3373a59b5a'/>
<id>urn:sha1:f08e457cecece7fbbdad3add9defac3373a59b5a</id>
<content type='text'>
F15h and later use a portion of DRAM as a CC6 storage area. BIOS
programs D18F1x[17C:140,7C:40] DRAM Base/Limit accordingly by
subtracting the storage area from the DRAM limit setting. However, in
order for edac to consider that part of DRAM too, we need to include it
into the per-node range.

Signed-off-by: Borislav Petkov &lt;borislav.petkov@amd.com&gt;
</content>
</entry>
<entry>
<title>amd64_edac: Remove node interleave warning</title>
<updated>2011-04-26T14:18:12Z</updated>
<author>
<name>Borislav Petkov</name>
</author>
<published>2011-04-08T13:05:21Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=f030ddfb3752df36bb73285353374fc04feabb80'/>
<id>urn:sha1:f030ddfb3752df36bb73285353374fc04feabb80</id>
<content type='text'>
This warning was wrongfully added for a normal condition - intlvsel
actually selects the destination node when node interleaving is enabled
and it is not a mismatch. For a detailed example, see section 2.8.10.2
"Node Interleaving" in F10h BKDG.

Signed-off-by: Borislav Petkov &lt;borislav.petkov@amd.com&gt;
</content>
</entry>
<entry>
<title>EDAC: Remove debugging output in scrub rate handling</title>
<updated>2011-04-21T10:44:58Z</updated>
<author>
<name>Markus Trippelsdorf</name>
</author>
<published>2011-04-20T18:28:45Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=4949603a6fabf3a54cbd7be6df1681789abfca7d'/>
<id>urn:sha1:4949603a6fabf3a54cbd7be6df1681789abfca7d</id>
<content type='text'>
This patch removes superfluous debugging output in the sysfs scrub rate
handler. It also consolidates the error handling in the scrub rate
accessors.

Signed-off-by: Markus Trippelsdorf &lt;markus@trippelsdorf.de&gt;
Signed-off-by: Borislav Petkov &lt;borislav.petkov@amd.com&gt;
</content>
</entry>
<entry>
<title>amd64_edac: Fix potential memleak</title>
<updated>2011-03-29T16:19:06Z</updated>
<author>
<name>Borislav Petkov</name>
</author>
<published>2011-03-29T16:10:53Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=a9f0fbe2bbf328f869fc5ee5a12c6a4118c32689'/>
<id>urn:sha1:a9f0fbe2bbf328f869fc5ee5a12c6a4118c32689</id>
<content type='text'>
We check the pointers together but at least one of them could be invalid
due to failed allocation. Since we cannot continue if either of the two
allocations has failed, exit early by freeing them both.

Cc: &lt;stable@kernel.org&gt; # 38.x
Reported-by: Mauro Carvalho Chehab &lt;mchehab@redhat.com&gt;
Signed-off-by: Borislav Petkov &lt;borislav.petkov@amd.com&gt;
</content>
</entry>
</feed>
