From: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
To: Greg KH <greg@kroah.com>
Cc: mananth@in.ibm.com, benh@kernel.crashing.org, stable@kernel.org,
anton@samba.org, linux-kernel@vger.kernel.org
Subject: Re: [stable] [3/3] powerpc: rtas_flash needs to use rtas_data_buf
Date: Tue, 22 Mar 2011 14:26:38 +0530 [thread overview]
Message-ID: <20110322085638.GA14035@linux.vnet.ibm.com> (raw)
In-Reply-To: <20110321214501.GB9546@kroah.com>
* Greg KH <greg@kroah.com> [2011-03-21 14:45:01]:
> On Sat, Mar 19, 2011 at 11:46:58PM +0530, Kamalesh Babulal wrote:
> > powerpc: rtas_flash needs to use rtas_data_buf
> >
> > Commit: bd2b64a12bf55bec0d1b949e3dca3f8863409646 upstream
> >
> > When trying to flash a machine via the update_flash command, Anton received the
> > following error:
> >
> > Restarting system.
> > FLASH: kernel bug...flash list header addr above 4GB
> >
> > The code in question has a comment that the flash list should be in
> > the kernel data and therefore under 4GB:
> >
> > /* NOTE: the "first" block list is a global var with no data
> > * blocks in the kernel data segment. We do this because
> > * we want to ensure this block_list addr is under 4GB.
> > */
> >
> > Unfortunately the Kconfig option is marked tristate which means the variable
> > may not be in the kernel data and could be above 4GB.
> >
> > Instead of relying on the data segment being below 4GB, use the static
> > data buffer allocated by the kernel for use by rtas. Since we don't
> > use the header struct directly anymore, convert it to a simple pointer.
> >
> > Reported-By: Anton Blanchard <anton@samba.org>
> > Signed-off-by: Milton Miller <miltonm@bga.com
> > Tested-By: Anton Blanchard <anton@samba.org>
> > Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
> > Signed-off-by: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
> > ---
> > arch/powerpc/kernel/rtas_flash.c | 41 ++++++++++++++++++++-----------------
> > 1 files changed, 22 insertions(+), 19 deletions(-)
>
> This diffstat differs from what the original commit had:
> arch/powerpc/kernel/rtas_flash.c | 39 +++++++++++++++++++++------------------
> 1 file changed, 21 insertions(+), 18 deletions(-)
>
> So I went with the original commit, ok?
>
Sorry, my bad the mismatch was due to the indentation difference in the hunk
@@ -592,8 +589,8 @@ static void rtas_flash_firmware(int reboot_type)
unsigned long rtas_block_list;
int i, status, update_token;
- if (rtas_firmware_flash_list.next == NULL)
- return; /* nothing to do */
+ if (rtas_firmware_flash_list == NULL)
+ return; /* nothing to do */
will make sure, it does not happens again.
> Why are you diverging from the original?
>
> thanks,
>
> greg k-h
Kamalesh
prev parent reply other threads:[~2011-03-22 8:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-19 18:16 [3/3] powerpc: rtas_flash needs to use rtas_data_buf Kamalesh Babulal
2011-03-21 21:45 ` [stable] " Greg KH
2011-03-22 8:56 ` Kamalesh Babulal [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=20110322085638.GA14035@linux.vnet.ibm.com \
--to=kamalesh@linux.vnet.ibm.com \
--cc=anton@samba.org \
--cc=benh@kernel.crashing.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mananth@in.ibm.com \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).