Date: Tue, 30 Jun 2020 15:38:59 +0200 From: Alexander Leidinger <Alexander@leidinger.net> To: Edward Tomasz =?utf-8?b?TmFwaWVyYcWCYQ==?= <trasz@freebsd.org> Cc: emulation@freebsd.org Subject: Re: [Bug 230160] linuxulator doesn't implement madvise(MADV_DONTNEED) and any MADV_ flags with values >= 8 correctly Message-ID: <20200630153859.Horde.h7G-xufvRwckOE0FBCmjA7g@webmail.leidinger.net> In-Reply-To: <ECA054B9-EEEC-4D46-8085-5ABA9B0BEBE4@FreeBSD.org> References: <20200630102834.Horde.gx36pdJxf2UwP6pq0GMUAVL@webmail.leidinger.net> <ECA054B9-EEEC-4D46-8085-5ABA9B0BEBE4@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This message is in MIME format and has been PGP signed. --=_8Bq1hc4Vo-SKj6iwvgu0o_W Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Quoting Edward Tomasz Napiera=C5=82a <trasz@freebsd.org> (from Tue, 30 Jun= =20=20 2020=2012:45:12 +0100): >> On 30 Jun 2020, at 09:29, Alexander Leidinger=20=20 >>=20<Alexander@leidinger.net> wrote: >> >> =EF=BB=BFQuoting bugzilla-noreply@freebsd.org (from Thu, 25 Jun 2020=20= =20 >>=2020:31:29 +0000): >> >>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D230160 >>> >>> --- Comment #12 from commit-hook@freebsd.org --- >>> A commit references this bug: >>> >>> Author: markj >>> Date: Thu Jun 25 20:30:31 UTC 2020 >>> New revision: 362631 >>> URL: https://svnweb.freebsd.org/changeset/base/362631 >>> >>> Log: >>> Implement an approximation of Linux MADV_DONTNEED semantics. >> >> Hi, >> >> I've updated from r360373 to r362771. When I now try to start some=20=20 >>=20Steam games I get a new error message: >> linux: pid 80394 (ThreadPoolSingl): possibly incorrect MADV_DONTNEED >> >> There are several different processes with this message. What needs=20= =20 >>=20to be done to determine the "possibily incorrect" part? > > FWIW, I=E2=80=99m seeing those messages when running Python regression te= sts=20=20 >=20(python3.6 -m test -vW -x test_socket), although it doesn=E2=80=99t see= m to=20=20 >=20break anything. There are two possibilities: 1) There is no issue, and the message is not needed and it should be remo= ved. 2) There may be an issue, and it needs to be fixed. In this case it=20=20 would=20be interesting to know what the issue is, and maybe also to know=20= =20 how=20to detect if a particular program runs into the issue. Bye, Alexander. --=20 http://www.Leidinger.net=20Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF --=_8Bq1hc4Vo-SKj6iwvgu0o_W Content-Type: application/pgp-signature Content-Description: Digitale PGP-Signatur Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJe+0BzAAoJEBINsJsD+NiGPzQP/0HVLgaHeBpvolQF85El3Xm4 He6IQUE7BYGWP2O0V9ibl7ZP08Bv6Mfr36KVBU0yjH1/sz0W4bQmSk+H95/+aJtL 94szacGzWLahK6xWynKj7d0d7eUBKNlxwnKznmWWq6Xlh8HqFkw5nMRoPX59yr9u 9dfefL/+IuDwjU55rIZlZvk7pJ3s0o10KgQdrlGHHH2hbF1bmB6xe3Jtg3Sz5HU9 99uPi86iaxTlsaN3E2LCv8eVn46eKP+yDmKb1MapCrkssOZHl8f74TMdI2OVJKAd l0kfPcEuu0CAQSBslwdVR9wx0SsNDni5WOB7Axp9C61BOtoWkxWgwicbXL9aJqx+ Us7o1oruFk2EmGkK9we4mHiyPeTINaGbPeMEGWbuekAkJ53ZLVOTGaoVyoTgmKy4 K1UmcIdD/3IaEBt4ByX/8yKk5HowqOv3O6jZYsGn9tL6mFtwJ7QsqqrNi13CSDGP Ej9JxDY/2cVx6k104/T4c0inbZ/mF4fpVnanpFu2oIHNFlrXx75xKmEy8dex/vAJ Jse9HIYycHzP+oTGbSDs5vr/Y809TfzYz9eH9U9FDzeqQMcbOj3evcd7iCArnPwA 0KJ+Z+aZi8h4r0vtI/Mt3ANLCM1I+vci5tkFb2zemm/T6VXsLKVHQjzX6+wGPjGs JgwlaB5QXQ+3TCvPsb5y =UAqP -----END PGP SIGNATURE----- --=_8Bq1hc4Vo-SKj6iwvgu0o_W--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20200630153859.Horde.h7G-xufvRwckOE0FBCmjA7g>