linux-kernel - Re: [git pull] more vfs bits

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: <20150222025105.GC29656@ZenIV.linux.org.uk>
Date:	Sun, 22 Feb 2015 02:51:05 +0000
From:	Al Viro <viro@...IV.linux.org.uk>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-fsdevel <linux-fsdevel@...r.kernel.org>
Subject: Re: [git pull] more vfs bits

On Sat, Feb 21, 2015 at 06:19:45PM -0800, Linus Torvalds wrote:

> > dentry_inode -> something. d_opened_inode() might do, but I'm not sure -
> > still sounds a bit wrong to me.  What it's about is "the actual fs object
> > behind this name, maybe from upper fs, maybe showing through from underlying
> > layer"
> 
> Yeah, I think "d_backing_store_inode()" would probably be more along
> the lines, but that's a mouthful. Maybe shortened to
> "d_backing_inode()"?

Umm...  Works for me.  Let's do it this way, then:
	* rename those guys through the whole series
	* leave the "annotate the filesystems" bits to sit in a vfs.git
branch
	* slap trylock_super() + bugfixes I'd been doing today
(procfs and debugfs symlink removals racing with follow_link, oopsable;
double-copy in autofs dev_ioctl.c, with length not rechecked after
copying, theoretically oopsable + reasonably likely data leak) on top of queue
	* feed it through local tests and send an updated pull request later
tonight.
--
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/