Date: Mon, 23 Apr 2018 23:35:26 +0200 From: Tijl Coosemans <tijl@FreeBSD.org> To: Konstantin Belousov <kostikbel@gmail.com> Cc: src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org Subject: Re: svn commit: r332489 - in head: gnu/usr.bin/gdb/kgdb sys/conf sys/dev/dcons sys/dev/hyperv/vmbus/i386 sys/dev/ppc sys/dev/syscons sys/i386/conf sys/i386/i386 sys/i386/include sys/i386/include/pc sys... Message-ID: <20180423233526.2eb5aaab@kalimero.tijl.coosemans.org> In-Reply-To: <20180422205103.GX6887@kib.kiev.ua> References: <201804132030.w3DKUnFn050153@repo.freebsd.org> <20180422210656.29cb7d0a@kalimero.tijl.coosemans.org> <20180422192614.GW6887@kib.kiev.ua> <20180422205103.GX6887@kib.kiev.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 22 Apr 2018 23:51:03 +0300 Konstantin Belousov <kostikbel@gmail.com> wrote: > On Sun, Apr 22, 2018 at 10:26:14PM +0300, Konstantin Belousov wrote: >> On Sun, Apr 22, 2018 at 09:06:56PM +0200, Tijl Coosemans wrote: >>> Could this have broken the linux futex syscall? I have a linux program >>> that gets stuck in linux_sys_futex and becomes unkillable. Note that the >>> routines in sys/i386/linux/linux_support.s try to do atomic operations on >>> user space addresses. >> >> Yes, it is quite possible. I will try to look next week. > > Try this. I only compile-tested it as a module. Yes, this fixes it. That was quick, thanks!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180423233526.2eb5aaab>