From: Steven Rostedt <rostedt@goodmis.org>
To: Bernd Petrovitsch <bernd@firmix.at>
Cc: Linus Torvalds <torvalds@osdl.org>,
Puneet Vyas <vyas.puneet@gmail.com>,
Jan Engelhardt <jengelh@linux01.gwdg.de>,
Grant Coady <lkml@dodo.com.au>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: [PATCH] make signal.c more readable (was: Re: xor as a lazy comparison)
Date: Mon, 25 Jul 2005 14:00:05 -0400 [thread overview]
Message-ID: <1122314405.6019.61.camel@localhost.localdomain> (raw)
In-Reply-To: <1122281833.10780.32.camel@tara.firmix.at>
Sorry for the double post. I added [PATCH] and changed the subject, and added Linus.
On Mon, 2005-07-25 at 10:57 +0200, Bernd Petrovitsch wrote:
> On Sun, 2005-07-24 at 18:15 -0400, Puneet Vyas wrote:
> [...]
> > I just compiled two identical program , one with "!=" and other with
> > "^". The assembly output is identical.
>
> Hmm, which compiler and which version?
> You might want to try much older and other compilers.
>
Doesn't matter. The cycles saved for old compilers is not rational to
have obfuscated code.
Here's the patch to make the code more readable.
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
--- linux-2.6.13-rc3/kernel/signal.c.orig 2005-07-25 13:50:20.000000000 -0400
+++ linux-2.6.13-rc3/kernel/signal.c 2005-07-25 13:50:51.000000000 -0400
@@ -665,8 +665,8 @@ static int check_kill_permission(int sig
(unsigned long)info != 2 && SI_FROMUSER(info)))
&& ((sig != SIGCONT) ||
(current->signal->session != t->signal->session))
- && (current->euid ^ t->suid) && (current->euid ^ t->uid)
- && (current->uid ^ t->suid) && (current->uid ^ t->uid)
+ && (current->euid != t->suid) && (current->euid != t->uid)
+ && (current->uid != t->suid) && (current->uid != t->uid)
&& !capable(CAP_KILL))
return error;
prev parent reply other threads:[~2005-07-25 18:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-24 16:40 xor as a lazy comparison Jan Engelhardt
2005-07-24 20:07 ` Grant Coady
2005-07-24 21:43 ` Jan Engelhardt
2005-07-24 22:15 ` Puneet Vyas
2005-07-25 8:57 ` Bernd Petrovitsch
2005-07-25 17:55 ` Steven Rostedt
2005-07-25 19:10 ` Lee Revell
2005-07-25 19:16 ` Philippe Troin
2005-07-25 19:18 ` Lee Revell
2005-07-26 6:07 ` Jan Engelhardt
2005-07-26 8:30 ` Bernd Petrovitsch
2005-07-25 19:24 ` Steven Rostedt
2005-07-25 19:27 ` Lee Revell
2005-07-25 19:23 ` Paulo Marques
2005-07-25 19:25 ` Lee Revell
2005-07-25 20:24 ` Bill Davidsen
2005-07-25 18:00 ` Steven Rostedt [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=1122314405.6019.61.camel@localhost.localdomain \
--to=rostedt@goodmis.org \
--cc=akpm@osdl.org \
--cc=bernd@firmix.at \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@dodo.com.au \
--cc=torvalds@osdl.org \
--cc=vyas.puneet@gmail.com \
/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