[lkml]   [2001]   [Nov]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH] remove BKL from drivers' release functions
    On Wed, Nov 28, 2001 at 04:26:16PM -0800, David C. Hansen wrote:
    > I wrote a quick and dirty char device driver to see if this happened.
    > If I run two tasks doing a bunch of opens and closes, the -EBUSY
    > condition in the open function does happen. Is my driver doing
    > something wrong?

    What's happening is:

    task 1 task 2
    -> sys_open
    -> lock_kernel
    -> testdev_open
    -> test_and_set_bit
    return success
    unlock kernel
    -> sys_open
    -> lock_kernel (blocks on it)
    -> testdev_open
    -> test_and_set_bit
    return -EBUSY
    unlock kernel

    The BKL is only held for the duration of the open, not until you close the

    Russell King ( The developer of ARM Linux

    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:13    [W:0.035 / U:25.384 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site