xfs
[Top] [All Lists]

Re: Filestreams (and 64bit inodes)

To: Eric Sandeen <sandeen@xxxxxxxxxxx>
Subject: Re: Filestreams (and 64bit inodes)
From: Greg Banks <gnb@xxxxxxxxxxxxxxxxx>
Date: Fri, 13 Jun 2008 13:57:24 +1000
Cc: markgw@xxxxxxx, Timothy Shimmin <tes@xxxxxxx>, Richard Scobie <richard@xxxxxxxxxxx>, xfs@xxxxxxxxxxx
In-reply-to: <4851EDB3.1010601@xxxxxxxxxxx>
Organization: File Serving Technologies ; Silicon Graphics Inc.
References: <484B15A3.4030505@xxxxxxxxxxx> <484CA425.3080606@xxxxxxxxxxx> <484DDDB3.70000@xxxxxxx> <484F0998.90306@xxxxxxxxxxx> <484F2CD7.9070506@xxxxxxx> <484F452A.8090909@xxxxxxxxxxx> <48512A34.1020604@xxxxxxxxxxx> <4851CD32.7080106@xxxxxxxxxxxxxxxxx> <4851E774.2070401@xxxxxxx> <4851EC2D.6010504@xxxxxxxxxxxxxxxxx> <4851EDB3.1010601@xxxxxxxxxxx>
Sender: xfs-bounce@xxxxxxxxxxx
User-agent: Thunderbird 1.5.0.12 (X11/20060911)
Eric Sandeen wrote:
> Greg Banks wrote:
>
>   
>>> (and the plan for statically linked apps? ...)
>>>       
>> Perhaps Fedora could enable the glibc magic for issuing warnings at link
>> time when those symbols are used, like what happens today if you use the
>> old unsafe gets() function:
>>
>> gnb@inara 1058> gcc -o fmeh x.c
>> /tmp/ccQhxIIo.o: In function `main':
>> x.c:(.text+0x18): warning: the `gets' function is dangerous and should not 
>> be used.
>>     
>
>
> It wouldn't help the automated builds (nobody'd see it)
Hmm.  I don't see a way in glibc to upgrade that warning to an error to
make those builds fail, at least in glibc 2.4.
>  but for normal
> user compilations that might be an option...
>
>   

Indeed.

-- 
Greg Banks, P.Engineer, SGI Australian Software Group.
The cake is *not* a lie.
I don't speak for SGI.


<Prev in Thread] Current Thread [Next in Thread>