Re: fix for 2.1.x ni65 module bug (and other similar drivers)

Alan Cox (alan@lxorguk.ukuu.org.uk)
Tue, 15 Sep 1998 18:48:31 +0100 (BST)

> > Why.. You are forcing a block of BSS (ie all zero) to be 0..
>
> why? only because most other drivers use the same initialzisation for
> their static array for device name and because I didn't know
> (and wasn't sure) that it's guaranteed [for all time] that these
> arrays are initialized with zero. as my problem showed, it's
> important that they _are_ initialized, so I thought better be sure...

Its been guaranteed since 0.9something.

> > The quote fixes stuff is definitely right. Constant strings may not
> > be writable
>
> hmm, non-writable strings would hit quite a number of network driver modules
> at this point...

Yep. It'll only show up on machines which pack constant strings in the code
segment and have non writeable code. I can only assume the OSF/Mach Linux
trees are entirely on platforms that dont pack constant text strings
in code..

Alan

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/