linux-kernel - Re: [PATCH 17/46] fs: Use rename lock and RCU for multi-step operations

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: <AANLkTinVP=OuJ-3u9pHdDuuKJoVrP4Unr5Dx1x=qHtXC@mail.gmail.com>
Date:	Wed, 19 Jan 2011 14:27:24 -0800
From:	Yehuda Sadeh Weinraub <yehudasa@...il.com>
To:	Nick Piggin <npiggin@...il.com>
Cc:	Nick Piggin <npiggin@...nel.dk>, linux-fsdevel@...r.kernel.org,
	linux-kernel@...r.kernel.org, Sage Weil <sage@...dream.net>,
	ceph-devel@...r.kernel.org
Subject: Re: [PATCH 17/46] fs: Use rename lock and RCU for multi-step operations

On Tue, Jan 18, 2011 at 2:42 PM, Nick Piggin <npiggin@...il.com> wrote:
> On Wed, Jan 19, 2011 at 9:32 AM, Yehuda Sadeh Weinraub

>> There's an issue with ceph as it references the
>> dentry->d_parent(->d_inode) at dentry_release(), so setting
>> dentry->d_parent to NULL here doesn't work with ceph. Though there is
>> some workaround for it, we would like to be sure that this one is
>> really required so that we don't exacerbate the ugliness. The
>> workaround is to keep a pointer to the parent inode in the private
>> dentry structure, which will be referenced only at the .release()
>> callback. This is clearly not ideal.
>
> Hmm, I'll have to think about it. Probably we can check for
> d_count == 0 rather than parent != NULL I think?
>

That'll solve ceph's problem, don't know about how'd affect other
stuff. We'll need to know whether this is the solution, or whether
we'd need to introduce some other band aid fix.

Thanks,
Yehuda
--
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/