Re: [PATCH] loop.c: respect bio barrier and sync

Sorry about the patch as attachments.

- You should handle sync_file() failure. If we don't have !f_op (will
  that ever hit, btw?) or ->fsync(), then fail the barrier with
  -EOPNOTSUPP. For fsync failure, well... You probably want to just
  error the bio with -EIO then.


Will fix.

- Does this work for all loop_device types?


What are the other loop_device types?

BTW, should/does an fsync on a block device translate into a disk flush?
I was looking at sync_blockdev and couldn't figure out how that happened.

Thanks,
-Costa
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

References:
- [PATCH] loop.c: respect bio barrier and sync
  - From: "Constantine Sapuntzakis" <[email protected]>
- Re: [PATCH] loop.c: respect bio barrier and sync
  - From: Jens Axboe <[email protected]>

Prev by Date: Re: Add a "enable" sysfs attribute to the pci devices to allow userspace (Xorg) to enable devices without doing foul direct access
Next by Date: Re: [PATCH] Move various PCI IDs to header file
Previous by thread: Re: [PATCH] loop.c: respect bio barrier and sync
Next by thread: [PATCH] drivers/block/loop.c: don't return garbage if LOOP_SET_STATUS not called
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]