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
| ||
|
Date: Tue, 10 Sep 2013 01:57:54 +0100 From: Al Viro <viro@...IV.linux.org.uk> To: George Spelvin <linux@...izon.com> Cc: torvalds@...ux-foundation.org, aswin@...com, john@...ffel.org, linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org, scott.norton@...com, Waiman.Long@...com Subject: Re: [PATCH v4 1/1] dcache: Translating dentry into pathname without taking rename_lock On Mon, Sep 09, 2013 at 08:40:20PM -0400, George Spelvin wrote: > I'm really wondering about only trying once before taking the write lock. > Yes, using the lsbit is a cute hack, but are we using it for its cuteness > rather than its effectiveness? > > Renames happen occasionally. If that causes all the current pathname > translations to fall back to the write lock, that is fairly heavy. > Worse, all of those translations will (unnecessarily) bump the write > seqcount, triggering *other* translations to fail back to the write-lock > path. _What_ "pathname translations"? Pathname resolution doesn't fall back to seq_writelock() at all. -- 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/
Powered by blists - more mailing lists