linux-ext4 - Re: Mixup with name_len & file

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: <20130311141856.GJ29799@quack.suse.cz>
Date:	Mon, 11 Mar 2013 15:18:56 +0100
From:	Jan Kara <jack@...e.cz>
To:	Theodore Ts'o <tytso@....edu>
Cc:	Jan Kara <jack@...e.cz>, linux-ext4@...r.kernel.org
Subject: Re: Mixup with name_len & file_type in e2fsprogs

On Thu 07-03-13 19:46:20, Ted Tso wrote:
> By the way, why was the application trying to access the directory
> entries directly, as opposed to using some of the higher level
> functions in libext2fs?  What was it trying to do?
  It was btrfs-convert (I could have told that in my original email as well
but it didn't seem important) - i.e. inplace convertor from ext4 to btrfs.
So it really needed to get the file type from the directory block to fill
in appropriate btrfs structures.

> Is there some new higher-level functionality we should be providing?
> Or was this just an application that didn't know about some better
> interface that it could have used?  Is this an open source
> application?  Can you send me a pointer to it?
  btrfs-convert is part of btrfsprogs so feel free to have a look. I don't
think we can actually provide some high level functionality to serve its
needs. It really just needs to do readdir(2) on fs image which is what is
already implemented in libext2fs.

								Honza
-- 
Jan Kara <jack@...e.cz>
SUSE Labs, CR
--
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