linux-kernel - Re: [PATCH] linux/magic.h for magic numbers

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]

Date:	Sat, 9 Sep 2006 15:33:34 +0200
From:	Sam Ravnborg <sam@...nborg.org>
To:	Jeff Garzik <jeff@...zik.org>
Cc:	Grzegorz Kulewski <kangur@...com.net>,
	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
	akpm@...l.org
Subject: Re: [PATCH] linux/magic.h for magic numbers

On Sat, Sep 09, 2006 at 09:24:22AM -0400, Jeff Garzik wrote:
> Grzegorz Kulewski wrote:
> >On Sat, 9 Sep 2006, Jeff Garzik wrote:
> >>An IRC discussion sparked a memory:  most filesystems really don't
> >>need to put anything at all in include/linux.  Excluding API-ish
> >>filesystems like procfs, just about the only filesystem symbols that
> >>get exported outside of __KERNEL__ are the *_SUPER_MAGIC symbols,
> >>and similar symbols.
> >>
> >>After seeing the useful attributes of linux/poison.h, I propose a
> >>similar linux/magic.h.
> >
> >But... if some patch changes this file (like adding new magic symbol) it 
> >will cause large part of the kernel to rebuild without any good reason. No?
> 
> No :)
> 
> * The days when linux/fs.h included individual filesystem headers is 
> long gone.  Only the filesystems themselves typically include the 
> linux/foo_fs*.h files these days.

But do we want one common set of magic numbers or do we try to divide it
up per subssystem. The lattter approach are used for many other purposes
so why not for magics too?
Or in other word magic.h => fs_magic.h

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