[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] [PATCH v1 1/6] docs: add feature document for Xen hypervisor sysfs-like support
- To: Ian Jackson <ian.jackson@xxxxxxxxxx>
- From: Jürgen Groß <jgross@xxxxxxxx>
- Date: Mon, 30 Sep 2019 10:17:26 +0200
- Cc: Stefano Stabellini <sstabellini@xxxxxxxxxx>, Wei Liu <wl@xxxxxxx>, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>, Andrew Cooper <Andrew.Cooper3@xxxxxxxxxx>, "Tim \(Xen.org\)" <tim@xxxxxxx>, George Dunlap <George.Dunlap@xxxxxxxxxx>, Julien Grall <julien.grall@xxxxxxx>, Jan Beulich <jbeulich@xxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxxx>
- Delivery-date: Mon, 30 Sep 2019 08:17:33 +0000
- List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
On 27.09.19 17:19, Ian Jackson wrote:
Jürgen Groß writes ("Re: [PATCH v1 1/6] docs: add feature document for Xen
hypervisor sysfs-like support"):
On 27.09.19 15:37, Ian Jackson wrote:
I think this is ASCII printing characters with the exception of
! " ` $ % ^ & * = + { } ' ~ < > / \ |
I struggle to find a principled explanation for this particular
exclusion set (apart from /), considering that following are
included:
- @ _ . : ( ) [ ] # , ;
Could we borrow some existing permitted character set ? If we are
permitting shell metacharacters why not just permit all printable
ASCII except / ?
Hmm, maybe we should allow just the "Posix portable file name character
set"? That would be [-._0-9A-Za-z]. And we should explicitly not allow
the key names "." and "..".
I agree about "." and "..".
I'm not sure the "Posix portable file name character set" is a very
good guide. Posix will be pretty restricted there. What is the legal
set in a Linux sysfs filename ?
Everything but "/" and "\0".
Do you mean "any 7-bit byte", or octet values 32-126 (0x20-0x7e)
inclusive, or something else ?
:-)
As I'd like to support e.g. the .config file contents of the hypervisor
build I guess I need (0x01-0xff) inclusive, right?
The .config file I have here does not seem to contain any control
characters. If it did surely that would be a bug? If you want this
you obviously do need to permit newlines and spaces and perhaps tabs
too.
.config can contain user supplied strings. While not making much sense
to have unprintable characters in there I don't see how to prevent them.
And I guess we'd want to see them in case such a weird .config was used
(and probably resulted in strange behavior).
Juergen
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel
|
