linux-kernel - Fwd: Linux hfsplus corrupts chflags bits?

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

Message-ID: <CAAcnjCTc2MuqvpznuUwBzoSu2NcX-fZqWO=O8yQLzy+g076d-w@mail.gmail.com>
Date:	Fri, 14 Sep 2012 15:53:19 +0200
From:	Paolo Giarrusso <p.giarrusso@...il.com>
To:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Fwd: Linux hfsplus corrupts chflags bits?

[Re-sending to LKML - it was rejected because my phone sent the mail
also in HTML.]

On Thu, Sep 13, 2012 at 11:35 PM, Matthew Garrett <mjg59@...f.ucam.org> wrote:
> There was a similar problem with the userflags field - we were writing
> random data.
Ouch, sorry for the noise! I'm pretty sure it's exactly the same
problem: I wrote rootflags but meant userflags.
I might be wrong, but I think that's the case because your bugfix was
merged after 3.3. Instead I was running 3.2.

Somewhat unrelatedly, I noticed that most flags can't be set even by
ioctl, so Linux backup utilities can't preserve those flags.
Is that something which could be fixed, say by exposing them as
extended attributes?

I'll doublecheck that all randomly set flags are indeed userflags. To
be sure: userflags contains flags which can be set by the owner, while
rootflags can only be altered by the superuser, right? So I can check
here on Darwin's man chflags
(https://developer.apple.com/library/mac/#documentation/Darwin/Reference/ManPages/10.6/man1/chflags.1.html)

Cheers,
--
Paolo 'Blaisorblade' Giarrusso - Ph.D. Student
http://www.informatik.uni-marburg.de/~pgiarrusso/
--
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/