mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Robert Love <rml@tech9.net>
To: torvalds@transmeta.com
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] remove fsuser()
Date: 04 Jun 2002 14:30:11 -0700	[thread overview]
Message-ID: <1023226211.3904.148.camel@sinai> (raw)

Linus,

Apparently nothing uses fsuser() - else I would of just stuck this on
the end the last patch...

This patch removes fsuser().  Now both suser() and fsuser() are gone and
all permission checks use an appropriate capable() call.

Patch is against 2.5.20 + previous suser() removal patch.  Please apply.

	Robert Love

diff -urN linux-2.5.20-rml/include/linux/sched.h linux/include/linux/sched.h
--- linux-2.5.20-rml/include/linux/sched.h	Tue Jun  4 14:18:57 2002
+++ linux/include/linux/sched.h	Tue Jun  4 14:20:38 2002
@@ -585,24 +585,6 @@
 extern void free_irq(unsigned int, void *);
 
 /*
- * This has now become a routine instead of a macro, it sets a flag if
- * it returns true (to do BSD-style accounting where the process is flagged
- * if it uses root privs). The implication of this is that you should do
- * normal permissions checks first, and check fsuser() last.
- *
- * suser() is gone, fsuser() should go soon too...
- */
-
-static inline int fsuser(void)
-{
-	if (!issecure(SECURE_NOROOT) && current->fsuid == 0) {
-		current->flags |= PF_SUPERPRIV;
-		return 1;
-	}
-	return 0;
-}
-
-/*
  * capable() checks for a particular capability.
  * See include/linux/capability.h for defined capabilities.
  */




                 reply	other threads:[~2002-06-04 21:30 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1023226211.3904.148.camel@sinai \
    --to=rml@tech9.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.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

all inboxes | Powered by JetHome®