mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: dmitrmax@gmail.com
Cc: linux-kernel@vger.kernel.org, sparclinux@vger.kernel.org
Subject: Re: [PATCH] Fix PCI resource mmaping on sparc64
Date: Fri, 31 Oct 2008 12:02:38 -0700 (PDT)	[thread overview]
Message-ID: <20081031.120238.156698095.davem@davemloft.net> (raw)
In-Reply-To: <eed7af970810310609o632034dia6140f7bec6fee66@mail.gmail.com>

From: "Max Dmitrichenko" <dmitrmax@gmail.com>
Date: Fri, 31 Oct 2008 16:09:48 +0300

Please post sparc patches to the sparclinux mailing list,
CC:'d

> There is a problem discovered in recent versions of ATI Mach64 driver
> in X.org on sparc64 architecture. In short, the driver fails to mmap
> MMIO aperture (PCI resource #2).
> 
> I've found that kernel's __pci_mmap_make_offset() returns EINVAL. It
> checks whether user attempts to mmap more than the resource length,
> which is 0x1000 bytes in our case. But PAGE_SIZE on SPARC64 is 0x2000
> and this is what actually is being mmaped. So __pci_mmap_make_offset()
> failed for this PCI resource.
> 
> Signed-off-by: Max Dmitrichenko <dmitrmax@gmail.com>
> 
> Code seems to be rather old. At least it was the same in 2.6.24. I
> have no explanation why this bug exposed only now. May be before X.org
> used to use some other method to mmap PCI resource into userspace (now
> it uses libpciaccess).
> 
> The patch is against 2.6.26. Greg, please consider to include it into
> the stable trees.

No, the sparc maintainer (that's me) will submit this patch to -stable
if it is correct and appropriate.

      reply	other threads:[~2008-10-31 19:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <eed7af970810310513h6c466ce5h7ada2013ab4053b1@mail.gmail.com>
2008-10-31 13:09 ` Max Dmitrichenko
2008-10-31 19:02   ` David Miller [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=20081031.120238.156698095.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=dmitrmax@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sparclinux@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®