lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sun, 4 Mar 2012 09:51:01 -0800 (PST)
From:	Hugh Dickins <hughd@...gle.com>
To:	Hillf Danton <dhillf@...il.com>
cc:	Linux-MM <linux-mm@...ck.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] mm: shmem: unlock valid page

On Sun, 4 Mar 2012, Hillf Danton wrote:
> In shmem_read_mapping_page_gfp() page is unlocked if no error returned,
> so the unlocked page has to valid.
> 
> To guarantee that validity, when getting page, success result is feed
> back to caller only when page is valid.
> 
> Signed-off-by: Hillf Danton <dhillf@...il.com>

I don't understand your description, nor its relation to the patch.

NAK to the patch: when no page has previously been allocated, the
SGP_READ case avoids allocation and returns NULL - do_shmem_file_read
then copies the ZERO_PAGE instead, avoiding lots of unnecessary memory
allocation when reading a large sparse file.

Hugh

> ---
> 
> --- a/mm/shmem.c	Sun Mar  4 12:17:42 2012
> +++ b/mm/shmem.c	Sun Mar  4 12:26:56 2012
> @@ -889,13 +889,13 @@ repeat:
>  		goto failed;
>  	}
> 
> -	if (page || (sgp == SGP_READ && !swap.val)) {
> +	if (page) {
>  		/*
>  		 * Once we can get the page lock, it must be uptodate:
>  		 * if there were an error in reading back from swap,
>  		 * the page would not be inserted into the filecache.
>  		 */
> -		BUG_ON(page && !PageUptodate(page));
> +		BUG_ON(!PageUptodate(page));
>  		*pagep = page;
>  		return 0;
>  	}
> --
> 
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ