From: Sandy Harris <sandy@storm.ca>
To: linux-kernel@vger.kernel.org
Subject: Re: struct page to 36 (or 64) bit bus address?
Date: Sat, 11 Aug 2001 12:13:09 -0400 [thread overview]
Message-ID: <3B755995.E876230C@storm.ca> (raw)
In-Reply-To: <20010809151022.C1575@sventech.com> <E15UvLO-0007tH-00@the-village.bc.nu> <15218.61869.424038.30544@pizda.ninka.net> <20010809163531.D1575@sventech.com> <20010811175626.O19169@athlon.random>
Andrea Arcangeli wrote:
> ... (the API says that if you get null out of the map call you
> should fallback, but no driver checks for this null retval and so in
> turn they're all prone to crash, not going to be fixed in 2.4 I guess).
That strikes me as a pretty basic programming error. Why on Earth is
it not considered a problem urgently needing a fix?
next prev parent reply other threads:[~2001-08-11 16:12 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-09 18:40 struct page to 36 (or 64) bit bus address? Johannes Erdfelt
2001-08-09 19:09 ` Alan Cox
2001-08-09 19:10 ` Johannes Erdfelt
2001-08-09 19:19 ` Alan Cox
2001-08-09 20:25 ` David S. Miller
2001-08-09 20:35 ` Johannes Erdfelt
2001-08-10 7:00 ` Gerd Knorr
2001-08-10 7:56 ` Johannes Erdfelt
2001-08-10 21:58 ` David S. Miller
2001-08-11 7:09 ` Gerd Knorr
2001-08-12 10:49 ` Write Combining (Write Coalescing) on memory mapped I/O on IA64 Steffen Persvold
2001-08-11 15:32 ` struct page to 36 (or 64) bit bus address? Jens Axboe
2001-08-11 15:56 ` Andrea Arcangeli
2001-08-11 16:13 ` Sandy Harris [this message]
2001-08-12 8:00 ` David S. Miller
[not found] <no.id>
2001-08-12 11:49 ` Alan Cox
2001-08-13 13:51 ` David S. Miller
2001-08-13 14:09 ` Alan Cox
2001-08-13 14:21 ` David S. Miller
2001-08-13 19:07 ` Gérard Roudier
2001-08-13 19:42 ` David S. Miller
2001-08-13 15:10 ` Alan Cox
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=3B755995.E876230C@storm.ca \
--to=sandy@storm.ca \
--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