Skip to contentSkip to conversation

sigsegv from rstpd on ppc

Bridge Butorina Lilya 2 participants 2 messages May 8, 2009 Ethernet bridge

lore
Share & tools
lore
#0 lore raw

Hi,

I want to run RSTP on ppc_8xx target, kernel 2.6.19.
Is there some recommendation or restriction from RSTP implementation for this condition?

I have a problem:
I ran rstpd-daemon on ppc and it dies in one minute after start with SIGSEGV exception. Debuging shows that the reason in epoll_list.c file , epoll_main_loop() function, one of element(ev) of epoll_event[] array:

ev[i].data.ptr->ref_ev = &ev[i];

This code kills rstpd.

Is this known problem? Where should I find solution?

Thanks.
Liliya.

#1 lore raw

What code are you using? And from where? All the code I can find in epoll_loop.c has things like:

for (i = 0; i < r; i++) {
    struct epoll_event_handler *p = ev[i].data.ptr;
    if (p != NULL)
      p->ref_ev = &ev[i];
}

Maybe ev[i].data.ptr is NULL and causing the crash. This can happen when we have indicated that we don't want epoll to tell us events for this fd anymore but an earlier event is still returned by epoll.

Another thing is that all the bridge changes needed for userspace STP are there only in Linux 2.6.22. So you will not be able to use rstpd on 2.6.19.

Quoted 23 lines · Butorina Lilya

Hi,

I want to run RSTP on ppc_8xx target, kernel 2.6.19.
Is there some recommendation or restriction from RSTP implementation for this condition?

I have a problem:
I ran rstpd-daemon on ppc and it dies in one minute after start with SIGSEGV exception. Debuging shows that the reason in epoll_list.c file , epoll_main_loop() function, one of element(ev) of epoll_event[] array:

ev[i].data.ptr->ref_ev = &ev[i];

This code kills rstpd.

Is this known problem? Where should I find solution?

Thanks.
Liliya.
_______________________________________________
Bridge mailing list
[email protected]
https://lists.linux-foundation.org/mailman/listinfo/bridge