Re: [RFC] tcp md5 use of alloc_percpu
From: Crestez Dan Leonard <hidden>
Date: 2014-10-23 01:00:43
On 10/23/2014 02:38 AM, Jonathan Toppins wrote:
On 10/22/14, 2:55 PM, Crestez Dan Leonard wrote:quoted
sg_init_one does virt_addr on the pointer which assumes it is directly accessible. But the tcp_md5sig_pool pointer comes from alloc_percpu which can return memory from the vmalloc area after the pcpu_first_chunk is exhausted. This looks wrong to me. I'm am getting crashes on mips and I believe this to be the cause.Thinking about this more if the issue really is sg_init_one assumes a directly accessible memory region, can we just modify the zone allocation to GFP_DMA using alloc_percpu_gfp()? Does this satisfy the assumptions made by sg_init_one?
I don't think that alloc_percpu_gfp can be used that way. Looking at the code it only checks for GFP_KERNEL and behaves "atomically" if it is not present. This means that it fails rather than vmalloc a new percpu_chunk. The problem is not that the memory is not allocated with GFP_DMA but rather that the memory is allocated with vmalloc. Regards, Leonard