mirror of
https://gitlab.com/libvirt/libvirt.git
synced 2025-02-01 17:35:17 +00:00
virPCIVPDResourceIsValidTextValue: Adjust comment to reflect actual code
The function does not reject '&', '<', '>' contrary to what it actually states. Move and adjust the comment. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Ján Tomko <jtomko@redhat.com>
This commit is contained in:
parent
36e11cca83
commit
42df6cc1b4
@ -167,19 +167,15 @@ virPCIVPDResourceGetFieldValueFormat(const char *keyword)
|
||||
* value or text field value. The expectations are based on the keywords specified
|
||||
* in relevant sections of PCI(e) specifications
|
||||
* ("I.3. VPD Definitions" in PCI specs, "6.28.1 VPD Format" PCIe 4.0).
|
||||
*
|
||||
* The PCI(e) specs mention alphanumeric characters when talking about text fields
|
||||
* and the string resource but also include spaces and dashes in the provided example.
|
||||
* Dots, commas, equal signs have also been observed in values used by major device vendors.
|
||||
*/
|
||||
bool
|
||||
virPCIVPDResourceIsValidTextValue(const char *value)
|
||||
{
|
||||
size_t i = 0;
|
||||
/*
|
||||
* The PCI(e) specs mention alphanumeric characters when talking about text fields
|
||||
* and the string resource but also include spaces and dashes in the provided example.
|
||||
* Dots, commas, equal signs have also been observed in values used by major device vendors.
|
||||
* The specs do not specify a full set of allowed code points and for Libvirt it is important
|
||||
* to keep values in the ranges allowed within XML elements (mainly excluding less-than,
|
||||
* greater-than and ampersand).
|
||||
*/
|
||||
|
||||
if (value == NULL)
|
||||
return false;
|
||||
|
Loading…
x
Reference in New Issue
Block a user