Re: [PATCH] Huge TLB: Potential NULL deref inarch/x86/mm/hugetlbpage.c:huge_pmd_share()

[Andrew Morton]

On Thu, 3 Feb 2011 22:17:53 +0100 (CET)
Jesper Juhl <jj@xxxxxxxxxxxxx> wrote:

> Document that NULL deref will never happen post find_vma() in 
> huge_pmd_share().
> 
> Signed-off-by: Jesper Juhl <jj@xxxxxxxxxxxxx>
> ---
>  hugetlbpage.c |    5 +++++
>  1 file changed, 5 insertions(+)
> 
> diff --git a/arch/x86/mm/hugetlbpage.c b/arch/x86/mm/hugetlbpage.c
> index 069ce7c..7dd2d5f 100644
> --- a/arch/x86/mm/hugetlbpage.c
> +++ b/arch/x86/mm/hugetlbpage.c
> @@ -61,6 +61,11 @@ static int vma_shareable(struct vm_area_struct *vma, unsigned long addr)
>  static void huge_pmd_share(struct mm_struct *mm, unsigned long addr, pud_t *pud)
>  {
>  	struct vm_area_struct *vma = find_vma(mm, addr);
> +	/*
> +	 * There is no potential NULL deref here. mmap_sem is held and
> +	 * caller knows that the virtual address at `addr' is within a
> +	 * vma, so find_vma() will never return NULL here.
> +	 */
>  	struct address_space *mapping = vma->vm_file->f_mapping;
>  	pgoff_t idx = ((addr - vma->vm_start) >> PAGE_SHIFT) +
>  			vma->vm_pgoff;

Not really.

That mmap_sem is held and that `addr' refers to a known-to-be-present
VMA are part of huge_pmd_share()'s interface.  They are preconditions
which must be satisfied before the function can be used.

So they should be documented as such, in the function's documentation. 
In fact they're the *most important* thing to document about the
function because they are subtle and unobvious from the implementation
and from the function signature and name.

>From an understandability/maintainability POV the code is crap.  It's yet
another example of kernel developers' liking for pointing machine guns
at each other's feet.

Really, some poor schmuck needs to go in and reverse-engineer all the
secret interface requirements and document them.  But we shouldn't let
a chance go by - a nice kerneldoc description for huge_pmd_share()
would be appreciated.  One which documents both the explicit and the
implicit calling conventions.

--
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/