Date: Tue, 29 Dec 2020 20:03:54 +0000 From: Edward Tomasz Napierala <trasz@freebsd.org> To: Jessica Clarke <jrtc27@freebsd.org> Cc: "src-committers@freebsd.org" <src-committers@freebsd.org>, "dev-commits-src-all@freebsd.org" <dev-commits-src-all@freebsd.org>, "dev-commits-src-main@freebsd.org" <dev-commits-src-main@freebsd.org> Subject: Re: git: 89e3d5671ba1 - main - bsnmpclient(3): make it thread-safe Message-ID: <X%2BuLqtSo/YTW8sg0@brick> In-Reply-To: <DBC0C62C-1280-4ADE-BF03-18D781330E5A@freebsd.org> References: <202012291500.0BTF0vGw034594@gitrepo.freebsd.org> <DBC0C62C-1280-4ADE-BF03-18D781330E5A@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 1229T1511, Jessica Clarke wrote: [..] > Is there really a documented requirement for everything to be called > from the same thread? I can see consumers of the library that already > use proper locking breaking because of this. I'm not aware of such requirement being documented; guess I was bit too much fixated on the one use case this patch fixes. Given that harti@ mentioned he's planning to get rid of global data, and other problems pointed out here, I think it's best to just revert it.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?X%2BuLqtSo/YTW8sg0>