From: "Manfred Spraul" <manfred@colorfullife.com>
To: "Alan Cox" <alan@lxorguk.ukuu.org.uk>
Cc: "Daniel Jacobowitz" <dan@debian.org>,
<linux-kernel@vger.kernel.org>, "Andrew Morton" <akpm@zip.com.au>
Subject: Re: [PATCH?] Crash in 2.4.17/ptrace
Date: Mon, 28 Jan 2002 23:07:30 +0100 [thread overview]
Message-ID: <002101c1a848$383e6750$010411ac@local> (raw)
In-Reply-To: <E16VJu7-0001w0-00@the-village.bc.nu>
From: "Alan Cox" <alan@lxorguk.ukuu.org.uk>
> > For framebuffers addresses, there is no page structure, and then the
> > page reference count updates read/write to random memory.
>
> If it is a physical pci bus object why do we need to refcount it,
> surely "no page" is ok. Its just up to the driver not to do anything
> stupid and the core code to honour the pci/pci transfer quirks (or
> when faced with a hard one just say "no")
>
With multi-threaded apps, munmap() during O_DIRECT is possible. vma
structures don't contain a reference count.
For ptrace, taking the physical address from the PTE and ioremapping it
temporarily would work, but ...
--
Manfred
next prev parent reply other threads:[~2002-01-28 22:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-28 21:33 [PATCH?] Crash in 2.4.17/ptrace Manfred Spraul
2002-01-28 22:05 ` Alan Cox
2002-01-28 22:07 ` Manfred Spraul [this message]
2002-01-28 22:26 ` Daniel Jacobowitz
-- strict thread matches above, loose matches on Subject: below --
2002-01-28 20:32 Daniel Jacobowitz
2002-01-28 21:03 ` Andrew Morton
2002-01-28 21:19 ` Daniel Jacobowitz
2002-01-28 21:29 ` Andrew Morton
2002-01-28 21:55 ` Alan Cox
2002-01-28 22:12 ` Andrew Morton
2002-01-28 22:15 ` Benjamin Herrenschmidt
2002-01-28 23:57 ` Andrea Arcangeli
2002-01-28 23:54 ` Andrea Arcangeli
2002-01-29 5:35 ` Andrew Morton
2002-01-28 23:47 ` Andrea Arcangeli
2002-01-28 21:42 ` Andrew Morton
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='002101c1a848$383e6750$010411ac@local' \
--to=manfred@colorfullife.com \
--cc=akpm@zip.com.au \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dan@debian.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox