From: Arthur Corliss <corliss@digitalmages.com>
To: Tim Schmielau <tim@physik3.uni-rostock.de>
Cc: Rik van Riel <riel@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@osdl.org>
Subject: Re: [PATCH] Re: 2.6.x BSD Process Accounting w/High UID
Date: Sun, 7 Mar 2004 15:56:47 -0900 (AKST) [thread overview]
Message-ID: <Pine.LNX.4.58.0403071535290.1733@bifrost.nevaeh-linux.org> (raw)
In-Reply-To: <Pine.LNX.4.53.0403071820190.32060@gockel.physik3.uni-rostock.de>
On Sun, 7 Mar 2004, Tim Schmielau wrote:
> But the current tools are only broken for the few people using high UIDs
> (and generally on 64 bit archs, but that's a different story).
This is broken on x86 as well. I guess I still have to question the logic of
logging bad data, even if you think the data is infrequent at best. Keep in
mind that in my environment I'm not using high UIDs because I actually have
that many accounts, I'm using them because each employee uses their employee
ID as their UID, which simplifies management for me. Again, this most likely
isn't typical, but it's not irrational, either.
> We shouldn't require people to recompile their userspace tools in the
> middle of a stable kernel series. (OK, 2.6 has just started, but we don't
> want to offend people upgrading from 2.4, either.)
I can understand this argument, and I would certainly agree for things that
are commonly used. But given the state of the BSD accounting tools (a package
that hasn't had a public update since 1998, and which has non-high uid broken
bits in it as well) I would hazard a guess that the impacted users is going to
be minimal, at best.
> How about the patch below? It requires a change to userspace tools if you
> want to use high uids, but it dosn't break binary compatibility. It even
> allows userspace to check whether high UIDs are supported, and allows
> future incompatible format changes to be detected.
I like it, and the addition of ac_version is a great idea. I might alter the
comment about 64-bit machines in acct.c, though. 32-bit UIDs affects 32-bit
machines as well.
> Well, they are not totally meaningless since we clip at the maximum
> representable value instead of wrapping around.
:-P I don't look at this any different than the byte-clipping we're doing with
UIDs. If we're logging data that's wrong, then you can't do accurate
accounting, period.
--Arthur Corliss
Bolverk's Lair -- http://arthur.corlissfamily.org/
Digital Mages -- http://www.digitalmages.com/
"Live Free or Die, the Only Way to Live" -- NH State Motto
next prev parent reply other threads:[~2004-03-08 0:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-04 18:04 [PATCH] " Arthur Corliss
2004-03-04 19:51 ` Rik van Riel
2004-03-04 20:39 ` Arthur Corliss
2004-03-04 21:54 ` Tim Schmielau
2004-03-04 22:33 ` Arthur Corliss
2004-03-07 17:45 ` [PATCH] " Tim Schmielau
2004-03-07 21:20 ` Tim Schmielau
2004-03-08 0:56 ` Arthur Corliss [this message]
2004-03-08 9:08 ` Tim Schmielau
2004-03-08 9:37 ` Arthur Corliss
2004-03-09 16:16 ` [PATCH] " Jeremy Jackson
2004-03-09 18:22 ` Tim Schmielau
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=Pine.LNX.4.58.0403071535290.1733@bifrost.nevaeh-linux.org \
--to=corliss@digitalmages.com \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@redhat.com \
--cc=tim@physik3.uni-rostock.de \
--cc=torvalds@osdl.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
all inboxes | Powered by JetHome®