mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: viro@parcelfarce.linux.theplanet.co.uk
To: Valdis.Kletnieks@vt.edu
Cc: kevin conaway <kconaway_is@yahoo.com>, linux-kernel@vger.kernel.org
Subject: Re: Where does user_path_walk() live?
Date: Sun, 12 Oct 2003 22:41:33 +0100	[thread overview]
Message-ID: <20031012214133.GO7665@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <200310122059.h9CKxweb019804@turing-police.cc.vt.edu>

On Sun, Oct 12, 2003 at 04:59:58PM -0400, Valdis.Kletnieks@vt.edu wrote:
> On Sun, 12 Oct 2003 21:38:19 BST, viro@parcelfarce.linux.theplanet.co.uk said:
> > On Sun, Oct 12, 2003 at 01:26:09PM -0700, kevin conaway wrote:
> > > I am a student doing an independent study on
> > > filesystem security and I was trying to pin down
> > 
> > man find
> > man xargs
> > man grep
> > 
> > RTFUnixFAQ
> 
> Actually, the answer Kevin wanted was:
> 
> cd /usr/src/linux
> grep -r __user_walk .

Ehh...  First of all, you'll end up doing a metric buttload of getdents()
for no good reason every time you want to search for something.  And on
the kernel source that's pretty noticable.

Moreover, you generally do *not* want to deal with every file in the tree -
find . -name *.[chS] does it nicely, grep -r can't do that at all.

grep -r is a pointless GNUism.  It's not safer than find + xargs grep, it's
weaker than use of find and it's non-portable to boot...

      reply	other threads:[~2003-10-12 21:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-12 20:26 kevin conaway
2003-10-12 20:38 ` viro
2003-10-12 20:59   ` Valdis.Kletnieks
2003-10-12 21:41     ` viro [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=20031012214133.GO7665@parcelfarce.linux.theplanet.co.uk \
    --to=viro@parcelfarce.linux.theplanet.co.uk \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=kconaway_is@yahoo.com \
    --cc=linux-kernel@vger.kernel.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®