linux-kernel - Re: [PATCH] x86 new setup: use appropriate sections for code and data

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: <464C8B60.5040109@zytor.com>
Date:	Thu, 17 May 2007 10:05:36 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Alexander van Heukelum <heukelum@...lshack.com>
CC:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86 new setup: use appropriate sections for code and
 data

Alexander van Heukelum wrote:
> An intermediate elf file is generated for the 16-bit setup code.
> The generated code can be viewed using objdump -m i8086 -d. As it
> stands, it also tries to disassemble the bugger_off_msg, which
> results in garbage. This introduces two new sections to separate
> the code and the data part of the bootsector stub. It also moves
> some code from the .header section (a data section) to .inittext.
> 
> Signed-off-by: Alexander van Heukelum <heukelum@...lshack.com>
> ---
> 
> Hi,
> 
> I hope the new section names are ok? Alternatives would be
> .bstext/.bsdata or .floppytext/.floppydata.

I'd prefer .bstext or .bs_text and .bsdata/.bs_data; possibly .bsecttext
and .bsectdata.  The term "boot sector" for that particular piece of
code is firmly established.

	-hpa

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