linux-kernel - Re: [PATCH] sysfs: kill an extra put in sysfs_create

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]

Date:	Thu, 19 Jul 2007 01:20:40 +0900
From:	Tejun Heo <htejun@...il.com>
To:	Satyam Sharma <satyam.sharma@...il.com>
CC:	Gabriel C <nix.or.die@...glemail.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Christoph Lameter <clameter@....com>, gregkh@...e.de,
	miles.lane@...il.com
Subject: Re: [PATCH] sysfs: kill an extra put in sysfs_create_link() failure
 path

Satyam Sharma wrote:
>> On 7/18/07, Tejun Heo <htejun@...il.com> wrote:
>> > Satyam Sharma wrote:
>> > > On 7/18/07, Tejun Heo <htejun@...il.com> wrote:
>> > >> There is a subtle bug in sysfs_create_link() failure path.  When
>> > >> symlink creation fails because there's already a node with the same
>> > >> name, the target sysfs_dirent is put twice - once by failure path of
>> > >> sysfs_create_link() and once more when the symlink is released.
>> > >
>> > > The "symlink" is released? But the creation of the symlink is
>> > > precisely what failed here ... did it not?
>> > >
>> > >> Fix it by making only the symlink node responsible for putting
>> > >> target_sd.
>> > >
>> > > And again ... the changelog sounds confusing indeed, perhaps I'm
>> > > not familiar enough with sysfs symlink-related terminology/semantics.
>> > > Care to elaborate?
> 
> BTW, please do explain this one to me, if you can find the time :-)

A symlink node holds two sd's.  Its parent as all other sd nodes and the
sd the symlink point to.  When the symlink is released (its refcnt goes
to zero), it puts both.  In this bug, the symlink is released twice -
once in the error handling path and one more time when symlink is released.

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