From: Matteo Croce <technoboy85@gmail.com>
To: Alejandro Colomar <alx@kernel.org>
Cc: linux-man@vger.kernel.org, Matteo Croce <teknoraver@meta.com>
Subject: Re: [PATCH] proc.5: document 'subset' mount option.
Date: Tue, 14 May 2024 21:12:43 +0200 [thread overview]
Message-ID: <CAFnufp1XDhzF=+2QqFGg_Ji04nxpb_wh0CYRgee+q00FgcqbDw@mail.gmail.com> (raw)
In-Reply-To: <pvdvga6qc2dov7uo3r73epgs72hzwv5ioiya3jl6eddqxwsbaq@uk7xau6ljj4h>
Il giorno mar 14 mag 2024 alle ore 21:06 Alejandro Colomar
<alx@kernel.org> ha scritto:
>
> Hi Matteo,
>
> On Tue, May 14, 2024 at 08:43:49PM GMT, Matteo Croce wrote:
> > Il giorno mar 14 mag 2024 alle ore 20:08 Alejandro Colomar
> > <alx@kernel.org> ha scritto:
> > >
> > >
> > > What is the accepted format? A CSV of pid numbers?
> > >
> > > Have a lovely day!
> > > Alex
> > >
> >
> > Hi Alejandro,
> > It can only accept the literal "pid" string:
>
> Then 'pid' should be in bold (B), not italics (I).
>
Ok, I will send a v2
> > # mount -t proc proc_pid pid -o subset=pid
> > # mount |grep -w proc_pid
> > proc_pid on /tmp/proc/pid type proc (rw,relatime,subset=pid)
> >
> > # ll -d pid/{1,$$,cmdline,version}
> > ls: cannot access 'pid/cmdline': No such file or directory
> > ls: cannot access 'pid/version': No such file or directory
> > dr-xr-xr-x. 9 root root 0 May 14 09:43 pid/1
> > dr-xr-xr-x. 9 root root 0 May 14 09:43 pid/25146
>
> Hmmm, makes sense.
>
> So, it contains:
>
> /proc/<pid>
> /proc/<tid>
> /proc/self
> /proc/thread-self
>
> And all others are gone, right?
>
> Is anything else included? Or is anything within those dirs gone?
>
Exactly, self and thread-self are the only non-numeric entries in that
mounted procfs.
# ls pid |grep -vx '[[:digit:]]*'
self
thread-self
#
> >
> > perl -e 'for($t=0;;$t++){print chr($t*($t>>8|$t>>13)&255)}' |aplay
>
> lol! It keeps funny for a surprising long time.
>
:)
--
Matteo Croce
perl -e 'for($t=0;;$t++){print chr($t*($t>>8|$t>>13)&255)}' |aplay
next prev parent reply other threads:[~2024-05-14 19:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-14 17:54 [PATCH] proc.5: document 'subset' mount option technoboy85
2024-05-14 18:08 ` Alejandro Colomar
2024-05-14 18:43 ` Matteo Croce
2024-05-14 19:06 ` Alejandro Colomar
2024-05-14 19:12 ` Matteo Croce [this message]
2024-05-14 19:53 ` Alejandro Colomar
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='CAFnufp1XDhzF=+2QqFGg_Ji04nxpb_wh0CYRgee+q00FgcqbDw@mail.gmail.com' \
--to=technoboy85@gmail.com \
--cc=alx@kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=teknoraver@meta.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).