[OpenAFS-devel] Re: Weird interaction between libnss-afs and aklog

[Derrick Brashear]

On Tue, Nov 24, 2009 at 10:31 AM, Andrew Deason <adeason@sinenomine.net> wr=
ote:
> On Tue, 24 Nov 2009 15:53:28 +0100
> Jakub Witkowski <jpw@wszib.edu.pl> wrote:
>
>> The backtrace follows:
>> Program received signal SIGSEGV, Segmentation fault.
>> [Switching to Thread 0x7fd9c68ac700 (LWP 22199)]
>> 0x000000000042713f in rxi_Start (event=3D0x0, arg0=3D0x1380e00, arg1=3D0=
x0,
>> istack=3D0) at rx.c:5287 5287 =A0 =A0 =A0 struct rx_peer *peer =3D
>> call->conn->peer; (gdb) backtrace
>> #0 =A00x000000000042713f in rxi_Start (event=3D0x0, arg0=3D0x1380e00,
>> arg1=3D0x0, istack=3D0) at rx.c:5287 #1 =A00x00007fd9c4bff4f0 in
>> rxi_ReadProc () from /lib/libnss_afs.so.2 #2 =A00x00007fd9c4bffa70 in
>
> Okay, yeah, you're in libnss-afs. Talk to Adam Megacz, or wherever
> libnss-afs bugreports should go.
>
>> For me, it's intriguing that this /only/ happens for aklog. I have
>> tested various other tools, including a short test program to directly
>> test of getuid and getpwuid, everything works like it should.
>
> I would guess there's some odd interactions between applications that
> use RX that make calls into libnss-afs, but I wouldn't know.

There are, especially when mixing pthread and lwp Rx.

I had this fun with PAM in the 1990s.

--=20
Derrick