On 2015-09-25 17:38, Guillaume Nault wrote:
On Tue, Sep 22, 2015 at 04:47:48AM +0300, Denys Fedoryshchenko wrote:
Hi,
Sorry for late reply, was not able to push new kernel on pppoes
without
permissions (it's production servers), just got OK.
I am testing patch on another pppoe server with 9k
On Tue, Sep 22, 2015 at 04:47:48AM +0300, Denys Fedoryshchenko wrote:
> Hi,
> Sorry for late reply, was not able to push new kernel on pppoes without
> permissions (it's production servers), just got OK.
>
> I am testing patch on another pppoe server with 9k users, for ~3 days, seems
> fine. I
On Fri, Sep 25, 2015 at 06:02:42PM +0300, Denys Fedoryshchenko wrote:
> On 2015-09-25 17:38, Guillaume Nault wrote:
> >On Tue, Sep 22, 2015 at 04:47:48AM +0300, Denys Fedoryshchenko wrote:
> >>Hi,
> >>Sorry for late reply, was not able to push new kernel on pppoes without
> >>permissions (it's
Hi,
Sorry for late reply, was not able to push new kernel on pppoes without
permissions (it's production servers), just got OK.
I am testing patch on another pppoe server with 9k users, for ~3 days,
seems fine. I will test today
also on server that was experiencing crashes within 1 day.
On
On Fri, Jul 17, 2015 at 09:16:14PM +0300, Denys Fedoryshchenko wrote:
> Probably my knowledge of kernel is not sufficient, but i will try few
> approaches.
> One of them to add to pppoe_unbind_sock_work:
>
> pppox_unbind_sock(sk);
> +/* Signal the death of the socket. */
>
As i suspect, this kernel panic caused by recent changes to pppoe.
This problem appearing in accel-pppd (server), on loaded servers (2k
users and more).
Most probably related to changed pppoe: Use workqueue to die properly
when a PADT is received
I will try to reverse this and related patches.
Probably my knowledge of kernel is not sufficient, but i will try few
approaches.
One of them to add to pppoe_unbind_sock_work:
pppox_unbind_sock(sk);
+/* Signal the death of the socket. */
+sk-sk_state = PPPOX_DEAD;
I will wait first, to make sure this patch was
