Searched hist:"5 e7f1d433804450cdb5ba478d26742963e06b1bc" (Results 1 – 2 of 2) sorted by relevance
| /openbmc/linux/fs/orangefs/ |
| H A D | namei.c | diff 5e7f1d433804450cdb5ba478d26742963e06b1bc Mon Feb 12 09:49:24 CST 2018 Martin Brandenburg <martin@omnibond.com> orangefs: update attributes rather than relying on server
This should be a no-op now, but once inode writeback works, it'll be
necessary to have the correct attribute in the dirty inode.
Previously the attribute fetch timeout was marked invalid and the server
provided the updated attribute. When the inode is dirty, the server
cannot be consulted since it does not yet know the pending setattr.
Signed-off-by: Martin Brandenburg <martin@omnibond.com>
Signed-off-by: Mike Marshall <hubcap@omnibond.com>
|
| H A D | file.c | diff 5e7f1d433804450cdb5ba478d26742963e06b1bc Mon Feb 12 09:49:24 CST 2018 Martin Brandenburg <martin@omnibond.com> orangefs: update attributes rather than relying on server
This should be a no-op now, but once inode writeback works, it'll be
necessary to have the correct attribute in the dirty inode.
Previously the attribute fetch timeout was marked invalid and the server
provided the updated attribute. When the inode is dirty, the server
cannot be consulted since it does not yet know the pending setattr.
Signed-off-by: Martin Brandenburg <martin@omnibond.com>
Signed-off-by: Mike Marshall <hubcap@omnibond.com>
|