NetBSD-Bugs archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Fwd: Re: kern/51621: PT_ATTACH from a parent is unreliable



The following reply was made to PR kern/51621; it has been noted by GNATS.

From: Kamil Rytarowski <n54%gmx.com@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Fwd: Re: kern/51621: PT_ATTACH from a parent is unreliable
Date: Fri, 11 Nov 2016 13:47:49 +0100

 This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
 --oJqus1d4f6G0HeEnOdHL1BguGXo4pQ88w
 Content-Type: multipart/mixed; boundary="dsKGnfI3X6HaEQOXhfW3ExLxgujBpG2nV"
 From: Kamil Rytarowski <n54%gmx.com@localhost>
 To: gnats-bugs%NetBSD.org@localhost
 Message-ID: <c4691439-a9e0-263a-d066-cf5e2c955be5%gmx.com@localhost>
 Subject: Fwd: Re: kern/51621: PT_ATTACH from a parent is unreliable
 References: <Pine.NEB.4.64.1611112045310.10724%speedy.whooppee.com@localhost>
 In-Reply-To: <Pine.NEB.4.64.1611112045310.10724%speedy.whooppee.com@localhost>
 
 --dsKGnfI3X6HaEQOXhfW3ExLxgujBpG2nV
 Content-Type: text/plain; charset=windows-1252
 Content-Transfer-Encoding: quoted-printable
 
 
 
 
 -------- Forwarded Message --------
 Subject: Re: kern/51621: PT_ATTACH from a parent is unreliable
 Date: Fri, 11 Nov 2016 20:45:52 +0800 (PHT)
 From: Paul Goyette <paul%whooppee.com@localhost>
 To: Kamil Rytarowski <n54%gmx.com@localhost>
 
 On Fri, 11 Nov 2016, Kamil Rytarowski wrote:
 
 > On 11.11.2016 12:36, Paul Goyette wrote:
 >> This PR got me thinking....
 >>
 >> What happens if a child process attempts to attach to its own parent? =
 Do
 >> we get all the signalling correct?  Does the parent still succeed when=
 
 >> wait(2) for the child?
 >>
 >> Sorry, just thinking about possible pathological situations.  :)
 >>
 >
 > This is currently uncovered (we are talking only PT_ATTACH, as
 > PT_TRACE_ME is already functional). I will add a test for it as well.
 >
 > There is another flaw, and I forgot to add it in the original PR; in th=
 e
 > documentation signal(7) redirects in SIGTRAP details to ptrace(2) but
 > there is no single word on SIGTRAP in the debugging interface man-page.=
 
 >
 > Signaling shall be described in details in ptrace(2) - not just that
 > something is stopped by a signal, but with a specification what exact
 > signal.
 >
 >
 > Can I CC gnats this message?
 
 Certainly!
 
 
 +------------------+--------------------------+------------------------+
 | Paul Goyette     | PGP Key fingerprint:     | E-mail addresses:      |
 | (Retired)        | FA29 0E3B 35AF E8AE 6651 | paul at whooppee.com   |
 | Kernel Developer | 0786 F758 55DE 53BA 7731 | pgoyette at netbsd.org |
 +------------------+--------------------------+------------------------+
 
 
 --dsKGnfI3X6HaEQOXhfW3ExLxgujBpG2nV--
 
 --oJqus1d4f6G0HeEnOdHL1BguGXo4pQ88w
 Content-Type: application/pgp-signature; name="signature.asc"
 Content-Description: OpenPGP digital signature
 Content-Disposition: attachment; filename="signature.asc"
 
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v2
 
 iQIcBAEBCAAGBQJYJb38AAoJEEuzCOmwLnZsnHYP/2nfu68T5PXgw68Zy7YOeDm0
 JZy5FRQRg3uYDA1Qvl+S+I88wUybSmmTfU9Wq0at+zhx7paI7rGwZBYcKaBBD/JX
 WT57JuEGDO9SFMXvN+jJ0dhI/wRg/vtnyAHO/UXsXl35msdyF4y+Ue3gUfQe7+Fw
 g3qXHykLksT5Tl9CeIvB8Arzr2xHqsv0B8hPavyVuyfQQ4hHUKsHfiFnnQBMRSf4
 elu2taKDKSNcVUx3LX3xJAmgESljdgFR5geJgNSuwW+8sgk3wpt0y+LQQlhWQgEo
 Irwwfqt3NCDE8czgBFpjZGiBZ4VCNvfQnMdPWQ8Gfb1ovwT71ZGpw63z3q3hF0cY
 rmf0aU4wbafyRJOhV0WXKOid3w168PatvSLVL50fRB8KfbXhO5aRyT2E3eqHjERv
 wMiXcyS9sXsqti3sApGI7+ElxBc97pYzIMJpKKM6WKqP5i0vC1z0wRD3V0XYSlk+
 I5P3O/m8cun6getGS1gGenfRyXALgsHqGkmnH6MPuFvk+F3n/N7dcsQi2D5PU3g2
 jh584nXGeZK8xkqGUaSa3+s4Wz95dxxcdVxstHx532IDLRIkOkZ9QqATtCtwNPn4
 FTVBBgGGgu12H+jZr+un67/7b7foOGzvSgnDz4W6JQBHw2liuP79XW0Sb22p2SBT
 cb0HUu99SzwvfUWAAlXA
 =y8ua
 -----END PGP SIGNATURE-----
 
 --oJqus1d4f6G0HeEnOdHL1BguGXo4pQ88w--
 


Home | Main Index | Thread Index | Old Index