Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 6 Nov 2011 20:10:41 +0200
From:      Kostik Belousov <kostikbel@gmail.com>
To:        Mikolaj Golub <trociny@freebsd.org>
Cc:        freebsd-hackers@freebsd.org, Robert Watson <rwatson@freebsd.org>
Subject:   Re: "ps -e" without procfs(5)
Message-ID:  <20111106181041.GH50300@deviant.kiev.zoral.com.ua>
In-Reply-To: <8662iyjof9.fsf@kopusha.home.net>
References:  <20111025082451.GO50300@deviant.kiev.zoral.com.ua> <86aa8k2im0.fsf@kopusha.home.net> <20111031094948.GB50300@deviant.kiev.zoral.com.ua> <86vcr21agm.fsf@kopusha.home.net> <20111105135801.GT50300@deviant.kiev.zoral.com.ua> <86ehxmpogp.fsf@kopusha.home.net> <20111105154443.GB50300@deviant.kiev.zoral.com.ua> <86ehxmjsza.fsf@kopusha.home.net> <20111105194553.GK50300@deviant.kiev.zoral.com.ua> <8662iyjof9.fsf@kopusha.home.net>

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

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

On Sat, Nov 05, 2011 at 10:37:46PM +0200, Mikolaj Golub wrote:
>=20
> On Sat, 5 Nov 2011 21:45:53 +0200 Kostik Belousov wrote:
>=20
>  KB> On Sat, Nov 05, 2011 at 08:59:21PM +0200, Mikolaj Golub wrote:
>  >>=20
>  >> On Sat, 5 Nov 2011 17:44:43 +0200 Kostik Belousov wrote:
>  >>=20
>  >>  >>  KB> I think that the aux vector must be naturally aligned. You c=
an return
>  >>  >>  KB> ENOEXEC early if vptr is not aligned.
>  >>  >>=20
>  >>  >> Not sure I see what you mean. vptr for auxv is calculated just co=
uple lines
>  >>  >> above, and I check the result here, in the part common for all ve=
ctor types.
>  >>  KB> You do not check for the alignment. Am I wrong ?
>  >>=20
>  >> I see now. If natural alignment means "addr % sizeof(aux) =3D=3D 0" t=
hen the aux
>  >> vectors are not naturally aligned. After adding this check:
>  >>=20
>  >>     if (vptr % sizeof(aux) !=3D 0)
>  >>             return (ENOEXEC);
>  KB> No, the natural alignment of the structure is the alignment of the m=
ost
>  KB> demanding member. So it is 4 bytes on 32bit, and 8 bytes on 64.
>=20
>  >>=20
>  >> I started to observe many ENOEXEC errors. Adding printf showed that t=
he
>  >> vectors are half size aligned.
>  >>=20
>  >> On i386:
>  >>=20
>  >> get_proc_vector(pid =3D getty[3442], type =3D 2): vptr (2143284876) %=
 sizeof(aux) (8) =3D 4)
>  >>=20
>  >> On amd64:
>  >>=20
>  >> get_proc_vector(pid =3D getty[2425], type =3D 2): vptr (1407374883465=
68) % sizeof(aux) (16) =3D 8)
>  >>=20
>  >> Looking at exec_copyout_strings() from kern_exec.c, how destp is calc=
ulated, I
>  >> think they are sizeof(char *) aligned.
>  >>=20
>  >> Do you think it is worth adding the check for sizeof(char *) alignmen=
t?
>  >>=20
>  >>     if (vptr % (sizeof(char *) !=3D 0)
>  >>             return (ENOEXEC);
>  KB> I suggest to use #if __ELF_WORD_SIZE =3D=3D 32 or 64.
>=20
> Thanks. The updated patch:
>=20
> http://people.freebsd.org/~trociny/env.sys.3.patch

Oops, I missed this in the previous review. You cannot use fubyte in
proc_read_mem(). fubyte reads a byte from the address space of the current
process. The fix is easy, use proc_rwmem for 1 byte.

I do not think that fall back to single byte read is warranted for
proc_read_mem calls e.g. for ps_strings. Add a flag to indicate whether
the proc_read_mem should fall back to byte read ?

I would prefer using sizeof(uint64_t) and sizeof(uint32_t) instead of 8
and 4 constants in the align checks.

Might be, add PROC_ASSERT_HELD() to get_ps_string() ?

procfs patch looks good.

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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (FreeBSD)

iEYEARECAAYFAk62zaEACgkQC3+MBN1Mb4icCACeJcDhyPfaGTk7frkifRXO5mUE
nYYAoMf82kNB6RVH1dmMK+DRmmYTcehs
=wxV9
-----END PGP SIGNATURE-----

--Y9J5124L7u056RQu--



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