Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 7 Sep 2012 18:59:36 +0300
From:      Konstantin Belousov <kostikbel@gmail.com>
To:        John Baldwin <jhb@freebsd.org>
Cc:        Sam Varshavchik <mrsam@courier-mta.com>, freebsd-hackers@freebsd.org
Subject:   Re: What happened to my /proc/curproc/file?
Message-ID:  <20120907155936.GY33100@deviant.kiev.zoral.com.ua>
In-Reply-To: <201209071033.52864.jhb@freebsd.org>
References:  <cone.1346723177.448775.23058.1000@monster.email-scan.com> <201209041210.07555.jhb@freebsd.org> <cone.1346802383.225884.23058.1000@monster.email-scan.com> <201209071033.52864.jhb@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help

--JIl7C0YrBDiPMQ28
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Sep 07, 2012 at 10:33:52AM -0400, John Baldwin wrote:
> On Tuesday, September 04, 2012 7:46:23 pm Sam Varshavchik wrote:
> > Is the dev+ino of what was exec()ed known, for another process? I might=
 be =20
> > able to get the client voluntarily submit its argv[0], then independent=
ly =20
> > have the server validate it by stat()ing that, and comparing the result=
 =20
> > against what the kernel says the process's inode is.
>=20
> It's known in the kernel certainly.  I don't think we currently have any =
way
> of exporting that info to userland however.

It is, as  KF_FD_TYPE_TEXT by sysctl kern.proc.filedesc.

--JIl7C0YrBDiPMQ28
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (FreeBSD)

iEYEARECAAYFAlBKGegACgkQC3+MBN1Mb4i84QCg87Qw1p4AuQZgMOKKOUlTTPDX
yPIAmgML6SmkH0bfsXpk44CCBn6x8o0o
=PbYe
-----END PGP SIGNATURE-----

--JIl7C0YrBDiPMQ28--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120907155936.GY33100>