[PATCH net-next 0/4] 6lowpan: set of bug fixes

[PATCH net-next 0/4] 6lowpan: set of bug fixes

[Tony Cheneau]

Hello,

(This is my first time submitting patches. If I fail to apply to
some rules in here, please let me know)

After reading the 6lowpan code, I found a few issues. This patchset
fixes them. This patchset should apply cleanly against the current
net-next. It contains only bug fixes, I'll send later on a few other
patches that will offer new functionalities.

This is a set of 4 small patches that correct bugs in 6lowpan:
- patch 1 fixes a potential crash when reassembling UDP fragments
- patch 2 fixes a type issues that prevent the fragmentation reassembly
  to operate properly.
- patch 3 and 4 corrects field encoding issues

Hope it helps.

Regards,
	Tony Cheneau

Re: [PATCH net-next 0/4] 6lowpan: set of bug fixes

[Tony Cheneau]

Hello,

As Jan pointed out, it seems that the third patch of my patchset is not 
formatted properly. Moreover, I got my own email address wrong. Please 
disregard the whole patchset as I need to investigate the issue. I'll 
repost the complete patchset when it will be resolved.

I'm sorry if it caused any of you to waste your time on it.

Regards,
Tony

Le 11.06.2012 06:37, Tony Cheneau a écrit :
> Hello,
>
> (This is my first time submitting patches. If I fail to apply to
> some rules in here, please let me know)
>
> After reading the 6lowpan code, I found a few issues. This patchset
> fixes them. This patchset should apply cleanly against the current
> net-next. It contains only bug fixes, I'll send later on a few other
> patches that will offer new functionalities.
>
> This is a set of 4 small patches that correct bugs in 6lowpan:
> - patch 1 fixes a potential crash when reassembling UDP fragments
> - patch 2 fixes a type issues that prevent the fragmentation 
> reassembly
>   to operate properly.
> - patch 3 and 4 corrects field encoding issues
>
> Hope it helps.
>
> Regards,
> 	Tony Cheneau
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html