From: Dave McCracken <dmccr@us.ibm.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2.5.30+] Second attempt at a shared credentials patch
Date: Thu, 08 Aug 2002 11:20:50 -0500 [thread overview]
Message-ID: <44050000.1028823650@baldur.austin.ibm.com> (raw)
In-Reply-To: <shsofcdfjt6.fsf@charged.uio.no>
--On Thursday, August 08, 2002 05:32:05 PM +0200 Trond Myklebust
<trond.myklebust@fys.uio.no> wrote:
> What the hell is that change to fs/nfs/dir.c below all about? Try
> mounting an NFSv2 partition with that applied...
Oops. Looks like I managed to make a mistake in merging. Here's a fixed
version:
http://www.ibm.com/linux/ltc/patches/misc/cred-2.5.30-4.diff.gz
> Instead of doing this as one big unreadable monolithic patch and
> risking getting things wrong like in the above case, it would be nice
> if you could go via a set of wrapper functions:
>
># define get_current_uid() (current->uid)
># define set_current_uid(a) current->uid = a
I don't see this as a win. I *could* do a big monolithic patch to change
all references to current->*id to macros, then change the macros in a
separate patch. But then we'd be stuck with macros for all those
references forever, and they're not likely to change again any time soon.
I don't think we'd really want to have macros for all our structure
references on the off chance that someone might change it in the future.
Dave McCracken
======================================================================
Dave McCracken IBM Linux Base Kernel Team 1-512-838-3059
dmccr@us.ibm.com T/L 678-3059
next prev parent reply other threads:[~2002-08-08 16:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-08 14:58 Dave McCracken
2002-08-08 15:32 ` Trond Myklebust
2002-08-08 16:20 ` Dave McCracken [this message]
2002-08-08 16:54 ` Trond Myklebust
2002-08-08 18:05 ` Dave McCracken
2002-08-08 19:56 ` Trond Myklebust
2002-08-08 20:11 ` Dave McCracken
2002-08-08 21:55 ` Trond Myklebust
2002-08-09 19:24 ` [PATCH 2.5.30+] Fourth " Dave McCracken
2002-08-09 19:51 ` Trond Myklebust
2002-08-09 20:51 ` Dave McCracken
2002-08-12 20:08 ` Trond Myklebust
2002-08-09 21:15 ` Linus Torvalds
2002-08-08 20:11 ` [PATCH 2.5.30+] Second " Trond Myklebust
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=44050000.1028823650@baldur.austin.ibm.com \
--to=dmccr@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/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
all inboxes | Powered by JetHome®