Re: Bug#842796: libc recently more aggressive about pthread locks in stable ?
On Sun, Nov 06, 2016 at 08:04:39AM +0100, Petter Reinholdtsen wrote:
> [Henrique de Moraes Holschuh]
> > And what should we do about Debian stretch, then?
>
> I believe a good start would be to add an assert() in a test version of
> glibc and then run all the autopkgtest scripts on the packages in the
> archive to see how widespread the problem is. It will not cover all
> packages, but at least a significant portion of the archive.
>
> I suspect we are too close to the Stretch freeze to try to modify all
> the packages affected by the problem,
>...
This discussion sounds as if all this would be future hardware,
but hardware with working (and not disabled) TSX is available
in nearly every computer shop in the world for over a year now
(the first fixed Intel CPUs were released in 2014).
Please don't make it sound as if TSX would be a huge problem for
stretch - it is not.
Every nontrivial piece of software has bugs.
If anyone wants to search specifically for this class of bugs that
is appreciated, just like searching for any other class of bugs is
appreciated.
Running stretch on hardware with TSX available and enabled
is working fine for many users for quite some time now.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
Reply to: