Re: m(un)map kmalloc buffers to userspace

[Sebastian Frias]

On 12/09/2015 03:32 PM, Michal Hocko wrote:
> On Wed 09-12-15 15:07:50, Marc Gonzalez wrote:
> > On 09/12/2015 14:55, Michal Hocko wrote:
> > > On Tue 08-12-15 18:25:31, Sebastian Frias wrote:
> > > > Hi,
> > > >
> > > > We are porting a driver from Linux 3.4.39+ to 4.1.13+, CPU is Cortex-A9.
> > > >
> > > > The driver maps kmalloc'ed memory to user space.
> > >
> > > This sounds like a terrible idea to me. Why don't you simply use the
> > > page allocator directly? Try to imagine what would happen if you mmaped
> > > a kmalloc with a size which is not page aligned? mmaped memory uses
> > > whole page granularity.
> >
> > According to the source code, this kernel module calls
> >
> >    kmalloc(1 << 17, GFP_KERNEL | __GFP_REPEAT);
>
> So I guess you are mapping with 32pages granularity? If this is really
> needed for internal usage you can use highorder page and map its
> subpages directly.
>
> > I suppose kmalloc() would return page-aligned memory?
>
> I do not think there is any guarantee like that. AFAIK you only get
> guarantee for the natural word alignment. Slab allocator is allowed
> to use larger allocation and put its metadata or whatever before the
> returned pointer.

Thanks for your answer.
Do you have any suggestions regarding the rest of the questions? 
(copy/pasted below for convenience)

2) Now that VM_RESERVED was removed, is there another recommended flag 
to replace it for the purposes above?
3) Since it was working before, we suppose that something that was 
previously done by default on the kernel it is not done anymore, could 
that be a remap_pfn_range during mmap or kmalloc?
4) We tried using remap_pfn_range inside mmap and while it seems to 
work, we still get occasional crashes due to corrupted memory (in this 
case the behaviour is the same between 4.1 and 3.4 when using the same 
modified driver), are we missing something?

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/