linux-kernel - Re: [PATCH -mm] Fix lseek on /proc/kcore

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1174569275.1158.175.camel@laptopd505.fenrus.org>
Date:	Thu, 22 Mar 2007 14:14:35 +0100
From:	Arjan van de Ven <arjan@...radead.org>
To:	Alexey Dobriyan <adobriyan@...ru>
Cc:	akpm@...l.org, Eric Dumazet <dada1@...mosbay.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH -mm] Fix lseek on /proc/kcore

On Thu, 2007-03-22 at 12:56 +0300, Alexey Dobriyan wrote:
> Signed-off-by: Alexey Dobriyan <adobriyan@...ru>
> ---
> 
>  fs/proc/inode.c |    5 +++--
>  1 file changed, 3 insertions(+), 2 deletions(-)
> 
> --- a/fs/proc/inode.c
> +++ b/fs/proc/inode.c
> @@ -167,8 +167,9 @@ static loff_t proc_reg_llseek(struct fil
>  	llseek = pde->proc_fops->llseek;
>  	spin_unlock(&pde->pde_unload_lock);
>  
> -	if (llseek)
> -		rv = llseek(file, offset, whence);
> +	if (!llseek)
> +		llseek = default_llseek;
> +	rv = llseek(file, offset, whence);
>  

this has potential impact way outside kcore......

did you audit all proc users to see if they can deal with lseek?

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