linux-kernel - Redesigning file2alias for easy merging (bits of kbuild/kconfig)

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: <E1IgSqZ-00032Y-02@flower>
Date:	Sat, 13 Oct 2007 00:19:06 +0200
From:	Oleg Verych <olecom@...wer.upol.cz>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	"added: Sam Ravnborg" <sam@...nborg.org>, Greg KH <gregkh@...e.de>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Redesigning file2alias for easy merging (bits of kbuild/kconfig)

* Thu, 11 Oct 2007 21:03:14 -0700 (PDT)

> On Thu, 11 Oct 2007, Greg KH wrote:
>
>> On Thu, Oct 11, 2007 at 07:58:04PM -0700, Linus Torvalds wrote:
>> > 
>> > So I merged it all, and I don't expect any problems, but I'm hoping 
>> > somebody is thinking about that mod_devicetable.h/file2alias.c mess.
>> > 
>> > I'm not entirely sure who to blame on that thing. I'm adding Greg to the 
>> > Cc, on the assumption that blaming him is usually the right thing to do ;)
>> 
>> Hey, it wasn't me this time, I haven't even built my trees for you to
>> pull from and break everything yet :)
>
> No, I meant more in the "who the hell is responsible for designing those 
> *files*" rather than who is responsible for the particular merge mess 
> that happened to involve them this time around.
>
>> But yeah, splitting up the mod_devicetable.h/file2alias.c mess is a very
>> good idea, I'll see what I can come up with tomorrow.
>
> I don't think it's a huge issue, but I wanted to bring it up because these 
> days we're normally so good with these kinds of things that it actually 
> stood out a bit. I used to do these kinds of nasty merges all the time 
> with init/main.c and the configuration files, until we split them up.
>
> So I'm certainly perfectly able and used to doing them, it's just that I 
> also think that we have generally learnt to do so much better.
>
> In other words: no hurry or pressure, I just wanted to bring it up, since 
> during the merge I got flashbacks to various "bad old times" that I had 
> hoped we had mostly left behind.
>
> Those files were originally designed/set up by Rusty. I could have blamed 
> him, or perhaps Sam as a kbuild guy, but the reason I cc'd you is that I 
> think this kind of smells like a "device model"ish thing...

If any amount of work will be done on (re)designing, i'd like to propose
documenting all that mod magic.

OK, it can be figured out from the code, and quick split+script_glue can
be "designed". But if goals and key points would be written in plain text
by person(s) who used to do and maintain it, that will be helpful.

Thanks.
____
-
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/