From: Andi Kleen <ak@suse.de>
To: Sorav Bansal <sbansal@stanford.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: BUG REPORT: User/Kernel Pointer bug in sys_poll
Date: 28 Oct 2004 08:32:58 +0200 [thread overview]
Message-ID: <p73d5z31het.fsf@verdi.suse.de> (raw)
In-Reply-To: <Pine.GSO.4.44.0410272246240.7124-100000@elaine9.Stanford.EDU.suse.lists.linux.kernel>
Sorav Bansal <sbansal@stanford.edu> writes:
> Older x86 architectures (386 and before) allow the kernel to write to any
> user location regardless of the write-protect bits.
Actually it's only some early steppings of 386 and Linux never ran on
a 286 or earlier. I think the best would be to just ignore it, the affected
user base is very likely zero or very near it. I suspect the
probability of one of these machines still used as a multiuser
machine is very definitely nil.
Cue is that 386 got occassionally broken, and it often took
months to be noticed.
These machines already have other exploitable bugs BTW that have been
ignored for a long time and only been fixed in 2.6.
So just ignore it. It's a non issue, really.
-Andi
next parent reply other threads:[~2004-10-28 6:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20041028052218.52478.qmail@web50207.mail.yahoo.com.suse.lists.linux.kernel>
[not found] ` <Pine.GSO.4.44.0410272246240.7124-100000@elaine9.Stanford.EDU.suse.lists.linux.kernel>
2004-10-28 6:32 ` Andi Kleen [this message]
2004-10-28 8:50 ` BUG REPORT: User/Kernel Pointer bug in sys_poll Denis Vlasenko
[not found] <20041028052218.52478.qmail@web50207.mail.yahoo.com>
2004-10-28 5:57 ` Sorav Bansal
2004-10-28 9:48 ` Andrew Morton
2004-10-28 10:04 ` Sorav Bansal
2004-10-28 19:24 ` Alan Cox
2004-10-28 4:25 Sorav Bansal
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=p73d5z31het.fsf@verdi.suse.de \
--to=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sbansal@stanford.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.