linux-ext4 - Re: [PATCH] ext4: Don't use 'struct dentry' for internal lookups

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: <alpine.LFD.1.10.0809211241330.4475@nehalem.linux-foundation.org>
Date:	Sun, 21 Sep 2008 12:48:01 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	"Theodore Ts'o" <tytso@....edu>
cc:	linux-ext4@...r.kernel.org
Subject: Re: [PATCH] ext4: Don't use 'struct dentry' for internal lookups



On Sat, 20 Sep 2008, Theodore Ts'o wrote:
> 
> Linus, I plan to push this to you at the next patch window; I'm just
> cc'ing you now since you authored the original patch.
> 
> It seems that the ext3 version of the patch seems not to have been
> picked up by akpm.  Want me to resend it to him?

That would be good. I guess we don't have any ext3 maintainer. But I also 
wouldn't object to just getting it through you if you want to.

> Also, per your complaints about the stack-heavy ext3 users, one fairly
> easy fix for x86_64 (the stack usage isn't all that bad on x86 when
> pointers are only 32-bits) is pretty much all of the places where we use
> "unsigned long" in fs/ext3 should be safely replaceable by "unsigned
> int" or "u32".  Sigh...

Somebody who knows the code should check it out, but yes.. I just checked 
that at least some versions of gcc will do the right thing, and only spill 
in 32 bits (I was worried that maybe gcc would end up spilling the whole 
64-bit register anyway).

				Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html