linux-kernel - Re: [PATCH 33/62] exofs: remove the second argument of k[un]map

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]

Message-ID: <4ED3C644.9040209@panasas.com>
Date:	Mon, 28 Nov 2011 09:35:00 -0800
From:	Boaz Harrosh <bharrosh@...asas.com>
To:	Cong Wang <amwang@...hat.com>
CC:	<linux-kernel@...r.kernel.org>, <akpm@...ux-foundation.org>,
	Benny Halevy <bhalevy@...ian.com>, <osd-dev@...n-osd.org>
Subject: Re: [PATCH 33/62] exofs: remove the second argument of k[un]map_atomic()

On 11/26/2011 09:27 PM, Cong Wang wrote:
> 
> Signed-off-by: Cong Wang <amwang@...hat.com>

Ack-by: Boaz Harrosh <bharrosh@...asas.com>

> ---
>  fs/exofs/dir.c |    4 ++--
>  1 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/fs/exofs/dir.c b/fs/exofs/dir.c
> index d0941c6..b757a6e 100644
> --- a/fs/exofs/dir.c
> +++ b/fs/exofs/dir.c
> @@ -597,7 +597,7 @@ int exofs_make_empty(struct inode *inode, struct inode *parent)
>  		goto fail;
>  	}
>  
> -	kaddr = kmap_atomic(page, KM_USER0);
> +	kaddr = kmap_atomic(page);
>  	de = (struct exofs_dir_entry *)kaddr;
>  	de->name_len = 1;
>  	de->rec_len = cpu_to_le16(EXOFS_DIR_REC_LEN(1));
> @@ -611,7 +611,7 @@ int exofs_make_empty(struct inode *inode, struct inode *parent)
>  	de->inode_no = cpu_to_le64(parent->i_ino);
>  	memcpy(de->name, PARENT_DIR, sizeof(PARENT_DIR));
>  	exofs_set_de_type(de, inode);
> -	kunmap_atomic(kaddr, KM_USER0);
> +	kunmap_atomic(kaddr);
>  	err = exofs_commit_chunk(page, 0, chunk_size);
>  fail:
>  	page_cache_release(page);

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