On Wed, 2021-09-08 at 13:25 +0800, Ian Kent wrote: > On Tue, 2021-09-07 at 06:35 -0500, Goldwyn Rodrigues wrote: > > Hi Ian, > > > > On 19:43 10/08, Ian Kent wrote: > > > On Mon, 2021-08-09 at 13:42 +0000, Sietse van Zanen wrote: > > > > > > > > If you're already aware and will relwase an update soon there's > > > > nothing > > > > more to do. Glibc 2.34 is not even a week old. I noticed that a > > > > few > > > > packages were running into this so I thought I'd notify their > > > > maintainers. > > > > > > I'll commit the change fairly soon and I hope I'll be able to > > > post > > > a release by the end of the month. > > > > When do you plan to make this release? If sometime later, could you > > post > > the patch removing _POSIX_THREAD_ATTR_STACKSIZE/PTHREAD_STACK_MIN? > > or > > update git? I don't want to deviate too much from upstream for our > > releases. > > Yes, I'm a bit behind. > I'll post the two patches later today, ;) Umm ... I have pushed changes up to the needed patch to the repo. The commit 91edcc55c681 "autofs-5.1.7 - use default stack size for threads" is the one your after. For this change I also had commit 7f711c687d41 "autofs-5.1.7 - eliminate some more alloca usage" but I don't think it's actually needed. The original problem was due to glibc usage of alloca(3) when getting group information for very large groups seen on Windows DCs IIRC. But for some time now glibc doesn't do this any more so all should be ok without the second patch. Clearly you'll get a conflict on the CHANGELOG if you don't have all the preceding patches from the repo. which is straight forward to fix. Ian
