linux-kernel - [announce] vfs-scale git tree update

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

Message-ID: <20110107075831.GA14915@amd>
Date:	Fri, 7 Jan 2011 18:58:31 +1100
From:	Nick Piggin <npiggin@...nel.dk>
To:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Al Viro <viro@...IV.linux.org.uk>,
	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: [announce] vfs-scale git tree update

Git tree is here:
  
  git://git.kernel.org/pub/scm/linux/kernel/git/npiggin/linux-npiggin.git
  
Branch is: vfs-scale-working

Head is: b3e19d924b6eaf2ca7d22cba99a517c5171007b6

Changes since last posting:
* Implemented Linus' suggestions:
  - Switch the filesystem methods in one hit rather than having _rcu
    variants. This avoids a lot of cruft from core code.
  - Implement filesystem rcu-walk aware conversions in seperate patches
    after the APIs are changed, making bisectability better.
  - Change dentry_memcmp to dentry_cmp
  - Rework the way ->d_revalidate is handled to be simpler.

* Fixed configfs bug caused by switching d_op on live dentry.

* Leave d_revalidate filesystem changes out for now. The sysfs one
  in particular seems to have been causing a funny regression.

* Bit more tweaking of changelogs documentation and comments.

* Passes ltp, xfstests, dbench stressing over nfs, and some of my own
  racer tests on a couple of filesystems. Needs wider testing.

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