Bug 1394063 - glfd offset should not be updated for positional read/write operations
Summary: glfd offset should not be updated for positional read/write operations
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: GlusterFS
Classification: Community
Component: libgfapi
Version: mainline
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-10 23:08 UTC by Raghavendra Talur
Modified: 2020-03-12 12:41 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-12 12:41:31 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

Description Raghavendra Talur 2016-11-10 23:08:54 UTC 
Description of problem:
posix defines that offset of an fd should not be updated after pread/preadv/pwrite/pwritev. Currently, gfapi has a different behavior that we update the glfd->offset after such operations.

Version-Release number of selected component (if applicable):
mainline


How reproducible:
always

Steps to Reproduce:
1. refer to tests/basic/gfapi/gfapi-pwrite-readv.c
Comment 1 Worker Ant 2016-11-10 23:11:13 UTC 
REVIEW: http://review.gluster.org/15821 (gfapi: offset should not be updated for positional read/write) posted (#1) for review on master by Raghavendra Talur (rtalur)
Comment 2 Worker Ant 2016-11-10 23:15:47 UTC 
REVIEW: http://review.gluster.org/15821 (gfapi: offset should not be updated for positional read/write) posted (#2) for review on master by Raghavendra Talur (rtalur)
Comment 4 Worker Ant 2020-03-12 12:41:31 UTC 
This bug is moved to https://github.com/gluster/glusterfs/issues/928, and will be tracked there from now on. Visit GitHub issues URL for further details
Note You need to log in before you can comment on or make changes to this bug.