public inbox for linux-audit@redhat.com
 help / color / mirror / Atom feed
From: Eric Paris <eparis@redhat.com>
To: William Roberts <bill.c.roberts@gmail.com>
Cc: Richard Guy Briggs <rgb@redhat.com>,
	William Roberts <wroberts@tresys.com>,
	linux-audit@redhat.com
Subject: Re: [PATCH] audit: Add cmdline to taskinfo output
Date: Wed, 30 Oct 2013 17:20:24 -0400	[thread overview]
Message-ID: <1383168024.28218.17.camel@flatline.rdu.redhat.com> (raw)
In-Reply-To: <CAFftDdoAoj3ySyHzZkS9nk43FK84YsHOZ0diuiz1ceAVsGO0cA@mail.gmail.com>

I'm like a child wandering into the middle of a movie and having no idea
what is going on.  But...

>         The limit is PATH_MAX. You could have an absolute path that
>         uses all available
>         characters.
>         
>         -Steve
> 
> 
> So looking at PATH_MAX...
> include/linux/limits.h:12:#define PATH_MAX        4096 /* # chars in a
> path name including nul */

I seem to recall that PATH_MAX is not really PATH_MAX  :)  It can be +10
ish...   for the " (deleted)" that gets appended if things are
unlinked...  just something I sorta recall rolling around the back of my
head and I haven't really any idea if it is applicable here in any
way...

  reply	other threads:[~2013-10-30 21:20 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-28 23:50 [PATCH] audit: Add cmdline to taskinfo output William Roberts
2013-10-29 15:14 ` Steve Grubb
2013-10-29 17:44   ` William Roberts
2013-10-29 17:55     ` William Roberts
2013-10-29 19:01     ` Steve Grubb
2013-10-29 19:12       ` William Roberts
2013-10-29 19:55         ` Steve Grubb
2013-10-29 20:25           ` William Roberts
2013-10-29 23:24             ` William Roberts
2013-10-30  0:43               ` William Roberts
2013-10-30 19:42                 ` Steve Grubb
2013-10-30 20:18                   ` William Roberts
2013-10-30 21:20                     ` Eric Paris [this message]
2013-10-30 21:52                       ` William Roberts
2013-10-31 14:36                     ` Steve Grubb
2013-10-31 15:24                       ` William Roberts
2013-10-31 15:28                         ` Richard Guy Briggs
2013-10-31 15:33                           ` William Roberts
2013-10-31 15:46                             ` Richard Guy Briggs
2013-10-31 15:51                               ` William Roberts
2013-10-31 15:52                                 ` William Roberts
  -- strict thread matches above, loose matches on Subject: below --
2013-10-28 23:47 William Roberts
2013-10-23 20:40 William Roberts
2013-10-24 19:10 ` Richard Guy Briggs
2013-10-28 13:48 ` William Roberts
2013-10-28 15:10   ` Richard Guy Briggs
2013-10-28 16:30     ` William Roberts
2013-10-28 19:02       ` William Roberts
2013-10-28 21:52         ` Richard Guy Briggs

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=1383168024.28218.17.camel@flatline.rdu.redhat.com \
    --to=eparis@redhat.com \
    --cc=bill.c.roberts@gmail.com \
    --cc=linux-audit@redhat.com \
    --cc=rgb@redhat.com \
    --cc=wroberts@tresys.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