linux-kernel - Re: [PATCH v4 1/1] dcache: Translating dentry into pathname without taking rename

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] [day] [month] [year] [list]

Date:	10 Sep 2013 04:24:27 -0400
From:	"George Spelvin" <linux@...izon.com>
To:	linux@...izon.com, viro@...IV.linux.org.uk
Cc:	aswin@...com, john@...ffel.org, linux-fsdevel@...r.kernel.org,
	linux-kernel@...r.kernel.org, scott.norton@...com,
	torvalds@...ux-foundation.org, Waiman.Long@...com
Subject: Re: [PATCH v4 1/1] dcache: Translating dentry into pathname without taking rename_lock

> _What_ "pathname translations"?  Pathname resolution doesn't fall back to
> seq_writelock() at all.

I meant the translation of dentry to pathname that this thread is about.
Apologies for my confusing abbreviation.  Since the reverse translation
(pathname to dentry) is done a level at a time and people understand
that it's not atomic, I agree with Linus that a livelock there is too
remote a possibility to worry about.
--
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/