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: <20180125074811.GA24022@L-66Y>
Date:   Wed, 24 Jan 2018 23:48:14 -0800
From:   Tyson Nottingham <tgnottingham@...il.com>
To:     "Darrick J. Wong" <darrick.wong@...cle.com>
Cc:     linux-ext4@...r.kernel.org, tytso@....edu, adilger.kernel@...ger.ca
Subject: Re: [PATCH] ext4: make huge file flag user visible.

On Tue, Jan 23, 2018 at 09:09:30PM -0800, Darrick J. Wong wrote:

> > Pardon my asking, but why is this necessary?  Are there
> > userspace-visible effects of this flag?
> 
> Ahh, the chattr man page says that 'h' means HUGE_FILE_FL, but I guess
> ext4 won't report it to userspace...?
> 
> <shrug> XFS won't either, maybe we just kill the 'h' option? :)

Thanks for responses. Yes, I was just trying to make ext4 consistent with the
man page. Since apparently the flag was intended to be user visible at some
point, I thought it would be fine to make it so. As you said, removing it from
chattr/lsattr is another option. I'll do whatever I'm told. :)

Tyson

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ