linux-kernel - Re: [PATCH] procfs: Fix refcnt leak on proc_self_follow

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: <20100113162504.1c06c5e6.akpm@linux-foundation.org>
Date:	Wed, 13 Jan 2010 16:25:04 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Al Viro <viro@...IV.linux.org.uk>
Cc:	OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>,
	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org
Subject: Re: [PATCH] procfs: Fix refcnt leak on proc_self_follow_link()
 error path

On Wed, 13 Jan 2010 19:43:01 +0000
Al Viro <viro@...IV.linux.org.uk> wrote:

> On Tue, Jan 12, 2010 at 03:38:36AM +0900, OGAWA Hirofumi wrote:
> > 
> > If ->follow_link handler return the error, it should decrement
> > nd->path refcnt.
> > 
> > This patch fix it.
> 
> It's OK for -stable, but for the next tree... not really.  I'd rather
> kill vfs_follow_link() uses here and in gfs2; see #untested in vfs-2.6.git
> for details.

Confused.  Is #untested planned for 2.6.33?  If not, how do we fix this
bug in .33?
--
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/