<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel/linux.git/drivers/char/ramoops.c, branch linux-2.6.35.y</title>
<subtitle>Linux kernel stable tree (mirror)</subtitle>
<id>https://git.radix-linux.su/kernel/linux.git/atom?h=linux-2.6.35.y</id>
<link rel='self' href='https://git.radix-linux.su/kernel/linux.git/atom?h=linux-2.6.35.y'/>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/'/>
<updated>2011-02-06T19:03:48+00:00</updated>
<entry>
<title>RAMOOPS: Don't overflow over non-allocated regions</title>
<updated>2011-02-06T19:03:48+00:00</updated>
<author>
<name>Ahmed S. Darwish</name>
<email>darwish.07@gmail.com</email>
</author>
<published>2010-12-25T09:57:09+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=bf4a80cbf1ec11260c1a458586f2433431646994'/>
<id>urn:sha1:bf4a80cbf1ec11260c1a458586f2433431646994</id>
<content type='text'>
commit 1873bb8115e678ad9fd0aac9dbbc68383bc36e06 upstream.

The current code mis-calculates the ramoops header size, leading to an
overflow over the next record at best, or over a non-allocated region at
worst.  Fix that calculation.

Signed-off-by: Ahmed S. Darwish &lt;darwish.07@gmail.com&gt;
Acked-by: Marco Stornelli &lt;marco.stornelli@gmail.com&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
Signed-off-by: Andi Kleen &lt;ak@linux.intel.com&gt;

</content>
</entry>
<entry>
<title>char drivers: RAM oops/panic logger</title>
<updated>2010-05-27T16:12:50+00:00</updated>
<author>
<name>Marco Stornelli</name>
<email>marco.stornelli@gmail.com</email>
</author>
<published>2010-05-26T21:43:54+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=56d611a04fb2db77334e06274de4daed92e2c626'/>
<id>urn:sha1:56d611a04fb2db77334e06274de4daed92e2c626</id>
<content type='text'>
Ramoops, like mtdoops, can log oops/panic information but in RAM.  It can
be used with persistent RAM for systems without flash support.  In
addition, for this systems, with this driver, it's no more needed add to
the kernel the mtd subsystem with advantage in footprint.

It can be used in a very easy way with persistent RAM for systems without
flash support.  For these systems, with this driver, it is no longer
required to cinlude mtd subsystem with an advantage in footprint.  In
addition, you can save flash space and store this information only in RAM.

Signed-off-by: Marco Stornelli &lt;marco.stornelli@gmail.com&gt;
Cc: Simon Kagstrom &lt;simon.kagstrom@netinsight.net&gt;
Cc: David Woodhouse &lt;David.Woodhouse@intel.com&gt;
Cc; Anders Grafstrom &lt;anders.grafstrom@netinsight.net&gt;
Cc: Yuasa Yoichi &lt;yuasa@linux-mips.org&gt;
Cc: Jamie Lokier &lt;jamie@shareable.org&gt;
Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
</feed>
