Bug #46985
closedcommon: validate type CephBool cause 'invalid command json'
0%
Description
while (!validate_cmd(m_cct, p->second.desc, cmdmap, errss)) {
++p;
if (p->first != prefix) {
delete f;
return on_finish(-EINVAL, "invalid command json", empty);
}
}
don't need to check prefix in while loop because previous already done.
Updated by Nathan Cutler over 3 years ago
- Project changed from Ceph to CephFS
- Status changed from New to Fix Under Review
- Pull request ID set to 36459
Updated by Patrick Donnelly over 3 years ago
- Assignee set to Yanhu Cao
- Target version set to v16.0.0
- Source set to Community (dev)
- Backport set to octopus,nautilus
Just this commit needs backported:
common: fix validate type CephBool cause 'invalid command json'
Fixes: https://tracker.ceph.com/issues/46985
Signed-off-by: Yanhu Cao <gmayyyha@gmail.com>
Updated by Patrick Donnelly over 3 years ago
- Status changed from Fix Under Review to Pending Backport
Updated by Nathan Cutler over 3 years ago
- Copied to Backport #47085: octopus: common: validate type CephBool cause 'invalid command json' added
Updated by Nathan Cutler over 3 years ago
- Copied to Backport #47086: nautilus: common: validate type CephBool cause 'invalid command json' added
Updated by Brad Hubbard over 3 years ago
- Related to Bug #47179: AdminSocket::do_accept() terminate called after throwing an instance of 'std::out_of_range' added
Updated by Brad Hubbard over 3 years ago
This change causes the failure seen in #47179. Could we either revert it or modify it so it reinstates the old behaviour?
Updated by Neha Ojha over 3 years ago
https://github.com/ceph/ceph/pull/37098 fixes a bug in https://github.com/ceph/ceph/pull/36459 and needs backport too.
Updated by Nathan Cutler over 3 years ago
Neha Ojha wrote:
https://github.com/ceph/ceph/pull/37098 fixes a bug in https://github.com/ceph/ceph/pull/36459 and needs backport too.
That's #47179 which has already been backported to octopus by https://github.com/ceph/ceph/pull/37341
Updated by Loïc Dachary about 3 years ago
- 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".