From: David Howells <dhowells@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: dhowells@redhat.com, viro@ftp.linux.org.uk, hch@infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: Credentials test patch
Date: Thu, 13 Sep 2007 22:19:01 +0100 [thread overview]
Message-ID: <1839.1189718341@redhat.com> (raw)
In-Reply-To: <alpine.LFD.0.999.0709131304510.16478@woody.linux-foundation.org>
Linus Torvalds <torvalds@linux-foundation.org> wrote:
> That "current_cred" thing is really too ugly to live.
Agreed.
> Why is it trying to make it look like a variable?
Like 'current' for instance?
static __always_inline struct task_struct *get_current(void)
{
return x86_read_percpu(current_task);
}
#define current get_current()
> That will just confuse people, and/or make them think it's a cheap thing
> rather than some complex function call.
Yes, I know it's silly.
One thing I was trying to do was make it possible to change how the cred
structure was accessed without having to keep going back and change a whole
load of stuff each time.
> IOW, this patch should be taken out and shot, for apparently actively
> trying to obfuscate what the heck is going on.
It's a 'test' patch, as you'll note from the subject, and not particularly
near completion. I'm interested in garnering useful comments, particularly on
the points of concern that I raised.
I have no intention of asking you to merge it as it stands - I was hoping that
would be clear.
David
next prev parent reply other threads:[~2007-09-13 21:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-13 19:56 Credentials test patch David Howells
2007-09-13 20:09 ` Linus Torvalds
2007-09-13 21:19 ` David Howells [this message]
2007-09-13 21:33 ` Linus Torvalds
2007-09-15 15:51 ` Ulrich Drepper
2007-09-17 11:02 ` David Howells
2007-09-17 14:28 ` Ulrich Drepper
2007-09-17 15:27 ` David Howells
2007-09-18 16:33 ` David Howells
2007-09-18 16:44 ` Trond Myklebust
2007-09-18 17:25 ` David Howells
2007-09-18 17:58 ` Casey Schaufler
2007-09-18 18:03 ` Trond Myklebust
2007-09-18 18:24 ` David Howells
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=1839.1189718341@redhat.com \
--to=dhowells@redhat.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@ftp.linux.org.uk \
/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