[lkml]   [2009]   [Jun]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH 0/4] FS: userspace notification of errors
    Andrew Morton wrote:
    > hm, I'm uncertain on the desirability or otherwise of the overall feature.
    > Are there users or distros or device manufacturers asking for this?
    > Where did the requirement come from?
    > What downstream application will handle the uevent messages? Do you
    > have some userspace design/plan in mind?
    > IOW, it would be useful if we were told more about all of this, rather
    > than just staring at a kernel patch!

    As the original idea came from me, while whole implementation
    and design was done by Denis, I'll comment on this.

    Our use-case is about hand-held devices. We are particularly
    working with large FAT volumes on MMC. Do not question please
    why it is FAT and not something else :-) Anyway, FAT is very
    unreliable, and often hits errors, in which case it simply
    switches to read-only mode, and usually prints something to
    the printk ring buffer.

    When FAT becomes read only out of the blue, the user-space
    reaction if very different. Often applications just start
    failing, dying, etc. From users' perspective, the hand-held
    just becomes weird.

    What we want instead is to teach FAT to send the user-space a
    notification. What our user-space people think to do is to
    catch the notification and show a dialog window which tells
    something like "Please, check your FS, blah blah", and may
    be offer the user to run fsck.vfat, not exactly sure.

    > One part of the design which you didn't describe, but which I inferred
    > is that you intend that userspace will see the FS_UNCLEAN=1 messages
    > and will then poll all the /sys/block/<bdev>/<part>/fs_unclean files to
    > work out which partition(s) got the error, correct? Please spell all
    > that out in the changelog.

    I think this part of the design needs more thought. Not
    all FSes have block devices (UBIFS, JFFS2), and some FSes
    may (theoretically) span more than one block device (btrfs?).

    Probably it is better to go without any sysfs file and
    just send udev events.

    > What use is the FS_UNCLEAN=0 message? I don't get that. Again, please
    > cover this in the description.

    Yes, the description should be improved. I think the idea is that
    we add an udev rule which invokes a certain user-space script/app
    on "FAT became R/O" events.

    Best Regards,
    Artem Bityutskiy (Артём Битюцкий)
    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: 2009-06-04 08:33    [W:0.023 / U:3.216 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site