[lkml]   [2003]   [Mar]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: 2.5.63 accesses below %esp (was: Re: ntfs OOPS (2.5.63))

    On 11 Mar 2003, Linus Torvalds wrote:
    > If there is a well-known list of compilers, we should put a BIG warning
    > in some core kernel file to guide people to upgrade (or maybe work

    Not enough, nobody would notice and today most end user doesn't
    compile the kernel himself, they are just shipped by a broken kernels.

    We *also* need a mechanism to know the kernel was compiled with a
    broken compiler (from kernel point of view of course, not the latest
    C++ features). Like the 'tainted' approach but this would be marked as
    broken/miscompiled/etc. To be able to tell the user *immediately* to
    complain to his vendor instead hunting/finding the bug again and
    again, as happening now.

    I know all compiler is broken but the severities are different.

    > around it by forcing -fno-frame-pointer if that fixes it for the
    > affected compilers).

    I also doubt this. There are things suppose the code was compiled

    > Do we have a list?

    Impossible. Vendors have their own versioning when they patch the

    Only way I see is to detect it at build time, BIG warning to the user
    of compiler, print a well visible "kernel was built by broken tools"
    message at boot time to end users and marking the kernel 'broken' in
    case it oopses for developers.

    And the badly broken compilers' case is closed. Once ..... well, at
    least for a given compiler bug, but the infrastructure would be there
    to deal with them in the future, if kernel can't workaround them.

    BTW, if possible having the Code both before and after when a fault
    happens could also help a lot in the future.

    And in general, an oops counter would be also useful, not spending too
    much time decoding potentialy bogus oopses.


    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2005-03-22 13:33    [W:0.019 / U:18.452 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site