On Tue, Jul 5, 2016 at 5:05 PM, Matt Bennett
wrote:
> On 07/06/2016 08:37 AM, Cong Wang wrote:
>> On Tue, Jul 5, 2016 at 10:59 AM, Cong Wang wrote:
>>> On Mon, Jul 4, 2016 at 7:50 PM, Matt Bennett
>>> wrote:
Using printk I have confirmed that ppp_pernet() is called from
ppp_connect_cha
On 07/06/2016 08:37 AM, Cong Wang wrote:
> On Tue, Jul 5, 2016 at 10:59 AM, Cong Wang wrote:
>> On Mon, Jul 4, 2016 at 7:50 PM, Matt Bennett
>> wrote:
>>> Using printk I have confirmed that ppp_pernet() is called from
>>> ppp_connect_channel() when the BUG occurs (i.e. pch->chan_net is NULL).
>>>
On Tue, Jul 5, 2016 at 10:59 AM, Cong Wang wrote:
> On Mon, Jul 4, 2016 at 7:50 PM, Matt Bennett
> wrote:
>> Using printk I have confirmed that ppp_pernet() is called from
>> ppp_connect_channel() when the BUG occurs (i.e. pch->chan_net is NULL).
>>
>> This behavior appears to have been introduce
On Mon, Jul 4, 2016 at 7:50 PM, Matt Bennett
wrote:
> Using printk I have confirmed that ppp_pernet() is called from
> ppp_connect_channel() when the BUG occurs (i.e. pch->chan_net is NULL).
>
> This behavior appears to have been introduced in commit 1f461dc ("ppp:
> take reference on channels net
Hi,
I am producing the attached bug trace when testing PPP connections.
Specifically the steps I am doing are:
1. Configure PPP client and LAC with shared key and wait for client to
negotiate an IP address.
2. Change the shared key on the LAC.
3. Bring the PPP client interface down and up to
