On Mon, Aug 30, 2021 at 10:45:47AM +0200, Martin Pieuchot wrote:
> On 06/08/21(Fri) 08:08, Theo Buehler wrote:
> > > The diff below fixes this by setting the "source" amap lock to the newly
> > > allocated one. This is not strictly necessary on OpenBSD since the amap
> > > is only inserted on the
On 06/08/21(Fri) 08:08, Theo Buehler wrote:
> > The diff below fixes this by setting the "source" amap lock to the newly
> > allocated one. This is not strictly necessary on OpenBSD since the amap
> > is only inserted on the global list at the end of amap copy, but this
> > satisfies the locking
On Fri, 6 Aug 2021 08:08:26 +0200
Theo Buehler wrote:
> > The diff below fixes this by setting the "source" amap lock to the
> > newly allocated one. This is not strictly necessary on OpenBSD
> > since the amap is only inserted on the global list at the end of
> > amap copy, but this satisfies
> The diff below fixes this by setting the "source" amap lock to the newly
> allocated one. This is not strictly necessary on OpenBSD since the amap
> is only inserted on the global list at the end of amap copy, but this
> satisfies the locking requirement of amap_wipeout() and is IMHO the
>
Hello Thomas,
Thanks a lot for your great but report, see below for an explanation and
a possible fix.
On 04/08/21(Wed) 12:18, Thomas L. wrote:
> >Synopsis: page fault trap in rw_status
> >Category: kernel
> >Environment:
> System : OpenBSD
>Synopsis: page fault trap in rw_status
>Category: kernel
>Environment:
System : OpenBSD 6.9
Details : OpenBSD 6.9 (GENERIC) #4: Mon Jun 7 08:20:14 MDT 2021
r...@syspatch-69-amd64.openbsd.org:/usr/src/sys/arch/amd64/compil
