Re: port-amd64/52696: SMAP breaks -current

[Kamil Rytarowski <n54%gmx.com@localhost>]

The following reply was made to PR port-amd64/52696; it has been noted by GNATS.

From: Kamil Rytarowski <n54%gmx.com@localhost>
To: Martin Husemann <martin%duskware.de@localhost>
Cc: gnats-bugs%NetBSD.org@localhost
Subject: Re: port-amd64/52696: SMAP breaks -current
Date: Sun, 5 Nov 2017 17:15:33 +0100

 This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
 --tlOvmPOXXsdXEBuV0MCQO965Tr9U9K5h3
 Content-Type: multipart/mixed; boundary="ij2q7Npnn1Rhn74td8fJsHJxHX0w5Jgc0";
  protected-headers="v1"
 From: Kamil Rytarowski <n54%gmx.com@localhost>
 To: Martin Husemann <martin%duskware.de@localhost>
 Cc: gnats-bugs%NetBSD.org@localhost
 Message-ID: <9129948c-fad1-7687-9645-244393b397aa%gmx.com@localhost>
 Subject: Re: port-amd64/52696: SMAP breaks -current
 References: <pr-port-amd64-52696%gnats.netbsd.org@localhost>
  <20171105031000.BA7137A1DE%mollari.NetBSD.org@localhost>
  <20171105100158.GB988%mail.duskware.de@localhost>
 In-Reply-To: <20171105100158.GB988%mail.duskware.de@localhost>
 
 --ij2q7Npnn1Rhn74td8fJsHJxHX0w5Jgc0
 Content-Type: text/plain; charset=utf-8
 Content-Language: en-US
 Content-Transfer-Encoding: quoted-printable
 
 On 05.11.2017 11:01, Martin Husemann wrote:
 > On Sun, Nov 05, 2017 at 03:10:00AM +0000, Kamil Rytarowski wrote:
 >>      391
 >>      392 	KASSERTMSG((!cpu_intr_p() && !cpu_softintr_p()),
 >>      393 	    "kmem(9) should not be used from the interrupt context")=
 ;
 >>      394 	v =3D3D kmem_intr_alloc(size, kmflags);
 >>      395 	KASSERT(v || (kmflags & KM_NOSLEEP) !=3D3D 0); /// <-- fired=
 
 >=20
 > Please do not collect random panics in a PR, it makes it hard to close =
 when
 > (like) two out of four are fixed.
 >=20
 > Martin
 >=20
 
 I was observing interleaved two types of panics with SMAP/SMEP messages
 and similar to this mentioned above in KASSERT()s. The previous ones
 weren't archived (no core creation successful, this time I took a photo).=
 
 
 I can imagine that returning NULL from an allocator can trigger
 SMAP/SMEP failure.
 
 The above one has been fixed:
 
 Module Name:	src
 Committed By:	mlelstv
 Date:		Sun Nov  5 07:49:45 UTC 2017
 
 Modified Files:
 	src/sys/kern: subr_pool.c
 
 Log Message:
 pool_grow can now fail even when sleeping is ok. Catch this case in pool_=
 get
 and retry.
 
 
 To generate a diff of this commit:
 cvs rdiff -u -r1.209 -r1.210 src/sys/kern/subr_pool.c
 
 
 --ij2q7Npnn1Rhn74td8fJsHJxHX0w5Jgc0--
 
 --tlOvmPOXXsdXEBuV0MCQO965Tr9U9K5h3
 Content-Type: application/pgp-signature; name="signature.asc"
 Content-Description: OpenPGP digital signature
 Content-Disposition: attachment; filename="signature.asc"
 
 -----BEGIN PGP SIGNATURE-----
 
 iQJABAEBCAAqFiEELaxVpweEzw+lMDwuS7MI6bAudmwFAln/OSYMHG41NEBnbXgu
 Y29tAAoJEEuzCOmwLnZsZ3kQALYWB3LX4QnXWiAtd21mfsAlrzqvwO76etdk4o7n
 k58ckD8tIV2aTcW/XKpucXmhFZeZkbKGNEYU4ELM9pTkRcXcBgXnnsNZ579cdDWk
 9/7k6XtfhNyCMoOOOVKCGG5mNbtsnQhBR+L7JkahJd4WOiKotJ9I3t/JCM3ok9WL
 pE+MoPCQY0qLy4Cqe6BTgqNUX+5cUDNIXuyw7BiAQsvmJVaa0391OkSkXDUtOznb
 XB+2RxhF6XWeV9SInIKZqRHUxjF5WFI3U4NadFjSUUIVYilrARgZvNrWkJ8XpK36
 D5jdGNJRLNfMy5OXGCwV2SK7BKft192jORB7YPXtCgm5isxP71V9nJed6ryrQ60u
 7/Z9WYCHn2308LxHevRSwQI/9u0cCgjVYzFoLDdSwCunJsssQdFAjkFX5Mj1kyvw
 zslPq/oENC0s5LT4J2SupkCigh7NWlxQoM1hAK8wp7zF3DpVSJg149R4oZK1sCdX
 Z/dGc7A7Dn1OlJMGmncxc9a4GLI81dSPyo9mxx/i+eOejRkImzG8d5nPknD+XY0s
 S9ujFTtmqKwd6v23C3byVhgp7s6xM1p5983+EozWL/t4DJMY7zUWcmBGp5Y8t7Ik
 nKdhdHgPJofa20PADcckSTX4eopnpc0Tn6j1dCtssO49a2bONGmeE2RjCYIgxfzz
 z1vL
 =ImrS
 -----END PGP SIGNATURE-----
 
 --tlOvmPOXXsdXEBuV0MCQO965Tr9U9K5h3--