diff options
| author | Jarek Poplawski <jarkao2@gmail.com> | 2010-08-11 02:02:10 +0000 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2010-08-17 17:37:28 -0700 |
| commit | e5093aec2e6b60c3df2420057ffab9ed4a6d2792 (patch) | |
| tree | f48c2c26c632adc44e5664bdea213b2f173f39f6 /include/linux | |
| parent | 1c40be12f7d8ca1d387510d39787b12e512a7ce8 (diff) | |
| download | kernel_samsung_smdk4412-e5093aec2e6b60c3df2420057ffab9ed4a6d2792.zip kernel_samsung_smdk4412-e5093aec2e6b60c3df2420057ffab9ed4a6d2792.tar.gz kernel_samsung_smdk4412-e5093aec2e6b60c3df2420057ffab9ed4a6d2792.tar.bz2 | |
net: Fix a memmove bug in dev_gro_receive()
>Xin Xiaohui wrote:
> I looked into the code dev_gro_receive(), found the code here:
> if the frags[0] is pulled to 0, then the page will be released,
> and memmove() frags left.
> Is that right? I'm not sure if memmove do right or not, but
> frags[0].size is never set after memove at least. what I think
> a simple way is not to do anything if we found frags[0].size == 0.
> The patch is as followed.
...
This version of the patch fixes the bug directly in memmove.
Reported-by: "Xin, Xiaohui" <xiaohui.xin@intel.com>
Signed-off-by: Jarek Poplawski <jarkao2@gmail.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'include/linux')
0 files changed, 0 insertions, 0 deletions