Bug #41871
closed
client: return error when someone passes bad whence value to llseek
Added by Jeff Layton over 4 years ago.
Updated about 4 years ago.
Description
There are a number of ceph_assert calls in src/client/Client.cc that are probably not necessary. There are calls in lseek and the file locking code in particular but there may be others. Do a cleanup pass through there and just have it return error instead of ceph_assert'ing when we can.
- Assignee set to Jeff Layton
- Subject changed from remove some ceph_asserts from libcephfs to remove some ceph_aborts from libcephfs
s/ceph_assert/ceph_abort/
- Subject changed from remove some ceph_aborts from libcephfs to don't ceph_abort when someone passes bad whence value to llseek
- Component(FS) Client added
- Target version set to v15.0.0
- Start date deleted (
09/16/2019)
- Source set to Development
- Backport set to nautilus,mimic
- Status changed from New to In Progress
- Subject changed from don't ceph_abort when someone passes bad whence value to llseek to client: return error when someone passes bad whence value to llseek
- Status changed from In Progress to Pending Backport
- Pull request ID set to 30580
- Copied to Backport #42145: nautilus: client: return error when someone passes bad whence value to llseek added
- Copied to Backport #42146: mimic: client: return error when someone passes bad whence value to llseek added
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".
Also available in: Atom
PDF