linux-kernel - Re: [PATCH 05/22][RFC] Unionfs: Copyup Functionality

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

Message-Id: <1158456535.17898.0.camel@localhost.localdomain>
Date:	Sat, 16 Sep 2006 21:28:55 -0400
From:	Shaya Potter <spotter@...columbia.edu>
To:	Josef Sipek <jsipek@....cs.sunysb.edu>
Cc:	Jan Engelhardt <jengelh@...ux01.gwdg.de>,
	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
	hch@...radead.org, akpm@...l.org, viro@....linux.org.uk
Subject: Re: [PATCH 05/22][RFC] Unionfs: Copyup Functionality

On Sat, 2006-09-16 at 18:13 -0400, Josef Sipek wrote:
> On Mon, Sep 04, 2006 at 12:41:58PM +0200, Jan Engelhardt wrote:
> > 
> > >> Is BUG the right thing, what do others think? (Using WARN, and set err to
> > >> something useful?)
> > > 
> > >Well, it is definitely a condition which Unionfs doesn't expect - if it
> > >doesn't know about the type, how could it copy it up?
> > 
> > Other filesystems don't seem to BUG either (at least I have not run into 
> > that yet) when - for whatever reasons - the statdata of a dentry is 
> > fubared. `ls`  just displays it then, like
> > 
> >  ?-w---Sr-T 1 root root 4294967295 date fubared_file
> 
> I was thinking about this, and the difference between "other filesystems"
> and unionfs in this case is that the example above is just stat. During
> copyup, unionfs has to copy the file to another filesystem. How is it
> supposed to do that when it doesn't understand what the file is?
> 
> Sure, when unionfs does stat, fubared statdata is fine, but during
> copyup...bad things could potentially happen.
> 
> Any suggestions how to copyup an unknown file type?

copyup is only required if a file is going to be modified.  refuse to
modify (or perhaps even open for write) an unknown file?  i.e. calling
BUG() is bad when it can be cleanly handled much earlier in the chain.

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