Nick Piggin wrote:

> Thanks, it confirms my suspicions.
> 
> Can you try the following patch, please?
> It appears the warnings were brought out by my improvement to
> the put_page_testzero debugging code (which previously did not
> check that we might be attempting to free a constituent compound
> page).
> 
> Can you test the following patch please?
> 

Sorry, wrong patch.

Note the warnings you are seeing should not result in memory
corruption, but will result in the given hugepage leaking.

-- 
SUSE Labs, Novell Inc.