linux-kernel - Re: Merge of the 'write_inode' branch from the VFS tree

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: <1267812155.5174.9.camel@localhost.localdomain>
Date:	Fri, 05 Mar 2010 13:02:35 -0500
From:	Trond Myklebust <Trond.Myklebust@...app.com>
To:	Al Viro <viro@...IV.linux.org.uk>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-nfs@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: Merge of the 'write_inode' branch from the VFS tree

On Fri, 2010-03-05 at 15:48 +0000, Al Viro wrote:

> Or I can do a new branch, put updated pair of patches there (hch has sent
> the updated variants my way) and ask you to rebuild NFS tree.  Which will
> also suck, since it adds PITA for you and you are completely innocent in
> that clusterfuck.
> 
> Suggestions?  I'd love to get out of that mess with minimal PITA for
> everyone involved and minimally messed tree...

Hi Al,

I'd be fine with rebuilding the NFS tree. I have all the patches which
depend on write_inode in their own separate branch anyway, so I'd only
have to rebase that branch and then merge it with the main NFS client
tree...

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