On 5/19/2011 11:24 AM, Ludovic Desroches wrote:

On 5/19/2011 10:04 AM, Barry Song wrote:

quoted

2011/5/19 Ludovic Desroches[off-list ref]:

quoted

Hello,

There is a bug with the atmel-mci driver when the debug feature
CONFIG_DEBUG_VM is set.

Into the atmci_read_data_pio function we use flush_dcache_page (do 
we really
need it?) which call the page_mapping function where we can find
VM_BUG_ON(PageSlab(Page)). Then a kernel panic happens.

I don't understand the purpose of the VM_BUG_ON(PageSlab(Page)) (the 
page
comes from a scatter list). How could I correct this problem?

linux/include/linux/mmdebug.h:

#ifdef CONFIG_DEBUG_VM
#define VM_BUG_ON(cond) BUG_ON(cond)
#else
#define VM_BUG_ON(cond) do { (void)(cond); } while (0)
#endif

it is something like "assert" in kernel.

Thanks for your answer but I know that. My question is more focused on 
why there is this check.

This the reason:

commit b5fab14e5d87df4d94161ae5f5e0c8625f9ffda2
Author: Christoph Lameter [off-list ref]
Date:   Tue Jul 17 04:03:33 2007 -0700

     Add VM_BUG_ON in case someone uses page_mapping on a slab page

     Detect slab objects being passed to the page oriented functions of 
the VM.

     It is not sufficient to simply return NULL because the functions 
calling
     page_mapping may depend on other items of the page_struct also to 
be setup
     properly.  Moreover slab object may not be properly aligned.  The page
     oriented functions of the VM expect to operate on page aligned, 
page sized
     objects.  Operations on object straddling page boundaries may only 
affect the
     objects partially which may lead to surprising results.

     It is better to detect eventually remaining uses and eliminate them.

Is flushing a page taken from a slab forbidden ? Is it risky ? Is it 
no sense ?

Other drivers do a flush_dcache_page on a page coming from a scatter 
list. So I think they will also have an assert when CONFIG_DEBUG_VM is set.

What is the proper way to do this flush (if needed) ?


Regards,

Ludovic