From: Marco Stornelli <marco.stornelli@gmail.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: "Ahmed S. Darwish" <darwish.07@gmail.com>,
Kyungmin Park <kyungmin.park@samsung.com>,
David Woodhouse <David.Woodhouse@intel.com>,
Greg KH <gregkh@suse.de>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH, Bugfix] RAMOOPS: Don't overflow over non-allocated regions
Date: Sat, 25 Dec 2010 12:19:35 +0100 [thread overview]
Message-ID: <4D15D347.6050500@gmail.com> (raw)
In-Reply-To: <20101225095709.GA1345@laptop>
Il 25/12/2010 10:57, Ahmed S. Darwish ha scritto:
> Hi,
>
> 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 <darwish.07@gmail.com>
> --
Acked-by: Marco Stornelli <marco.stornelli@gmail.com>
next prev parent reply other threads:[~2010-12-25 11:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-25 9:57 [PATCH, Bugfix] RAMOOPS: Don't overflow over non-allocated regions Ahmed S. Darwish
2010-12-25 11:19 ` Marco Stornelli [this message]
2010-12-27 21:33 ` Ahmed S. Darwish
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=4D15D347.6050500@gmail.com \
--to=marco.stornelli@gmail.com \
--cc=David.Woodhouse@intel.com \
--cc=akpm@linux-foundation.org \
--cc=darwish.07@gmail.com \
--cc=gregkh@suse.de \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@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 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.