From: Russell King <rmk+lkml@arm.linux.org.uk>
To: linux-kernel@vger.kernel.org
Subject: Re: [patch 18/39] remap_file_pages protection support: add VM_FAULT_SIGSEGV
Date: Mon, 15 Aug 2005 11:25:46 +0100 [thread overview]
Message-ID: <20050815112546.G19811@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20050815111548.F19811@flint.arm.linux.org.uk>; from rmk+lkml@arm.linux.org.uk on Mon, Aug 15, 2005 at 11:15:48AM +0100
On Mon, Aug 15, 2005 at 11:15:48AM +0100, Russell King wrote:
> On Mon, Aug 15, 2005 at 08:12:54PM +1000, Nick Piggin wrote:
> > Well there is now, and that is we are now using a bit in the 2nd
> > byte as flags. So I had to do away with -ve numbers there entirely.
> >
> > You could achieve a similar thing by using another bit in that byte
> > #define VM_FAULT_FAILED 0x20
> > and make that bit present in VM_FAULT_OOM and VM_FAULT_SIGBUS, then
> > do an unlikely test for that bit in your handler and branch away to
> > the slow path.
>
> That'll do as well, thanks.
Note that Ingo will not get replies from me anymore - Ingo is doing
sender callback checks on the From:/Sender: headers. Since my joejob
protection ensures that I never receive bounces to those addresses,
such callbacks fail. Hence his server rejects my messages.
I am not changing my policy on this - I get hammered with a tremendous
amount of such crap which tools like SA seem completely incapable of
dealing with, sorry.
(Note: this means that other folk, eg dwmw2, are in a similar position.)
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
next prev parent reply other threads:[~2005-08-15 10:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-12 18:21 [patch 18/39] remap_file_pages protection support: add VM_FAULT_SIGSEGV blaisorblade
2005-08-15 9:40 ` Russell King
2005-08-15 10:12 ` Nick Piggin
2005-08-15 10:15 ` Russell King
2005-08-15 10:25 ` Russell King [this message]
2005-08-23 8:45 ` Blaisorblade
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=20050815112546.G19811@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--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