linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: linux-ide@vger.kernel.org, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] siimage: fix kernel oops on PPC 44x
Date: Tue, 08 Apr 2008 17:09:57 +0400	[thread overview]
Message-ID: <47FB6EA5.4070606@ru.mvista.com> (raw)
In-Reply-To: <200804072330.00610.bzolnier@gmail.com>

Bartlomiej Zolnierkiewicz wrote:

>>Fix kernel oops due to machine check occuring in init_chipset_siimage() on PPC
>>44x platforms.  These 32-bit CPUs have 36-bit physical address and PCI I/O and
>>memory spaces are mapped beyond 4 GB; arch/ppc/ code has a fixup in ioremap()
>>that creates an illusion of the PCI I/O and memory resources being mapped below
>>4 GB, while arch/powerpc/ code got rid of this fixup with PPC 44x having instead
>>CONFIG_RESOURCES_64BIT=y -- this causes the resources to be truncated to 32-bit
>>'unsigned long' type in this driver, and so non-existant memory being ioremap'ed
>>and then accessed...

>>Thanks to Valentine Barshak for providing an initial patch and explanations.

>>Signed-off-by: Sergei Shtylyov <sshtylyov@ru.mvista.com>

> applied and pushed to Linus, thanks!

> I guess that it would be worth to audit the rest of IDE code for

    Already done. Some drivers, like sgiioc4, scc_pata, and pmac are prone to
that at least in theory.  Although I doubt that they ever get used in such
environments as PPC 44x platform kernels, i.e. 32-bit kernel and PCI mapped 
beyond 4 GB.

> pci_resource_{start,end}() vs 'unsigned long' occurences and fix them.

    There are quite a lot of those overall but they only pose danger if the 
resource in question is in memory space since the I/O space always uses 
'unsigned long' addresses. So, IDE core and drivers using only I/O resources 
should not be prone to that kind of issue.

> [ Even if they work at the moment they are just bugs waiting to happened
>   when we add support for some new platforms or rewrite the code... ]

WBR, Sergei


  reply	other threads:[~2008-04-08 13:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-07 20:05 [PATCH] siimage: fix kernel oops on PPC 44x Sergei Shtylyov
2008-04-07 21:29 ` Bartlomiej Zolnierkiewicz
2008-04-08 13:09   ` Sergei Shtylyov [this message]
2008-04-09 18:14     ` Bartlomiej Zolnierkiewicz

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=47FB6EA5.4070606@ru.mvista.com \
    --to=sshtylyov@ru.mvista.com \
    --cc=bzolnier@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.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).