linux-kernel - Re: [PATCH -mm] rescue large xfs preferred iosize from the inode diet patch

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: <20060922163415.4e137374.akpm@osdl.org>
Date:	Fri, 22 Sep 2006 16:34:15 -0700
From:	Andrew Morton <akpm@...l.org>
To:	Eric Sandeen <sandeen@...deen.net>
Cc:	Timothy Shimmin <tes@....com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	xfs mailing list <xfs@....sgi.com>
Subject: Re: [PATCH -mm] rescue large xfs preferred iosize from the inode
 diet patch

On Fri, 22 Sep 2006 18:19:18 -0500
Eric Sandeen <sandeen@...deen.net> wrote:

> Andrew Morton wrote:
> 
> >> So the fix for this is coming soon (and the fix is different from the
> >> one above).
> >>
> > 
> > eh?  Eric's patch is based on -mm, which includes the XFS git tree.  If I
> > go and merge the inode-diet patches from -mm, XFS gets broken until you
> > guys merge the above mystery patch.  (I prefer to merge the -mm patches
> > after all the git trees have gone, but sometimes maintainers dawdle and I
> > get bored of waiting).
> > 
> > Is git://oss.sgi.com:8090/nathans/xfs-2.6 obsolete, or are you hiding stuff
> > from me?  ;)
> > 
> > 
> well it's in cvs:

That's nearly four months old!

> http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/linux-2.6/xfs_iops.c.diff?r1=text&tr1=1.254&r2=text&tr2=1.253&f=h

<checks to see if the changelog is in Aramaic too>


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