RE:(2) (2) (2) (2) (2) [Kernel][NET] Bug report on packet defragmenting

>On 11/08/2018 04:42 PM, 배석진 wrote: >> Thanks for testing. >>> >>> This is not a pristine net-next tree, this dump seems unrelated to the  >>>patch ? >>  >>  >> yes, looks like that. >> but only when using your patch, panic came. even right after packet  >>recieving.. >> without that, there's no pr

Re: (2) (2) (2) (2) [Kernel][NET] Bug report on packet defragmenting

On 11/08/2018 04:42 PM, 배석진 wrote: >> Thanks for testing. >> >> This is not a pristine net-next tree, this dump seems unrelated to the patch >> ? > > > yes, looks like that. > but only when using your patch, panic came. even right after packet > recieving.. > without that, there's no problem

RE:(2) (2) (2) (2) [Kernel][NET] Bug report on packet defragmenting

>Thanks for testing. > >This is not a pristine net-next tree, this dump seems unrelated to the patch ? yes, looks like that. but only when using your patch, panic came. even right after packet recieving.. without that, there's no problem except defrag issue. it's odd.. :p I couldn't more debuggin

Re: (2) (2) (2) [Kernel][NET] Bug report on packet defragmenting

On 11/07/2018 11:58 PM, 배석진 wrote: >> - Original Message - >> Sender : Eric Dumazet  >> Date : 2018-11-08 15:13 (GMT+9) >> Title : Re: (2) (2) [Kernel][NET] Bug report on packet defragmenting >>   >> On 11/07/2018 08:26 PM, Eric Dumazet wrote: >>>   >>>   >>>  On 11/07/2018 08

RE:(2) (2) (2) [Kernel][NET] Bug report on packet defragmenting

>- Original Message - >Sender : Eric Dumazet  >Date : 2018-11-08 15:13 (GMT+9) >Title : Re: (2) (2) [Kernel][NET] Bug report on packet defragmenting >  >On 11/07/2018 08:26 PM, Eric Dumazet wrote: >>  >>  >> On 11/07/2018 08:10 PM, 배석진 wrote:  - Original Message -