From 31c03eaaf3424fb454c4768cc8df28a0c45bbddb Mon Sep 17 00:00:00 2001 From: Andrew Cooper Date: Thu, 28 Nov 2019 20:52:36 +0000 Subject: [PATCH] docs: Use https:// links in preference to http:// Signed-off-by: Andrew Cooper --- docs/mainpage.dox | 12 ++++++------ include/xen/errno.h | 2 +- make-new-test.sh | 2 +- tests/debug-regs/main.c | 10 +++++----- tests/xsa-122/main.c | 2 +- tests/xsa-123/main.c | 2 +- tests/xsa-167/main.c | 2 +- tests/xsa-168/main.c | 2 +- tests/xsa-170/main.c | 2 +- tests/xsa-173/main.c | 2 +- tests/xsa-182/main.c | 2 +- tests/xsa-183/main.c | 2 +- tests/xsa-185/main.c | 2 +- tests/xsa-186/main.c | 4 ++-- tests/xsa-188/main.c | 2 +- tests/xsa-191/main.c | 2 +- tests/xsa-192/main.c | 2 +- tests/xsa-193/main.c | 4 ++-- tests/xsa-194/main.c | 2 +- tests/xsa-195/main.c | 2 +- tests/xsa-196/main.c | 4 ++-- tests/xsa-200/main.c | 2 +- tests/xsa-203/main.c | 2 +- tests/xsa-204/main.c | 2 +- tests/xsa-212/main.c | 2 +- tests/xsa-213/main.c | 2 +- tests/xsa-221/main.c | 4 ++-- tests/xsa-224/main.c | 2 +- tests/xsa-227/main.c | 2 +- tests/xsa-231/main.c | 2 +- tests/xsa-232/main.c | 2 +- tests/xsa-234/main.c | 2 +- tests/xsa-239/main.c | 2 +- tests/xsa-255/main.c | 2 +- tests/xsa-259/main.c | 2 +- tests/xsa-260/main.c | 2 +- tests/xsa-261/main.c | 2 +- tests/xsa-265/main.c | 4 ++-- tests/xsa-269/main.c | 2 +- tests/xsa-277/main.c | 2 +- tests/xsa-278/main.c | 4 ++-- tests/xsa-279/main.c | 2 +- 42 files changed, 57 insertions(+), 57 deletions(-) diff --git a/docs/mainpage.dox b/docs/mainpage.dox index 7fd5cf6..4b09ce1 100644 --- a/docs/mainpage.dox +++ b/docs/mainpage.dox @@ -108,7 +108,7 @@ To run tests on a Xen host: (see @ref errata first) @section history History The Xen Test Framework grew out of the work done to debug -[XSA-106](http://xenbits.xen.org/xsa/advisory-106.html). As reported, Xen's +[XSA-106](https://xenbits.xen.org/xsa/advisory-106.html). As reported, Xen's instruction emulator failed to perform dpl checks for instructions generating software exceptions, which allowed guest userspace to bypass a security check set up by the guest kernel. Further investigation showed that the exception @@ -122,11 +122,11 @@ doing this, it was observed that different hardware was behaving differently not behaving as described in the manual. Once the embargo on XSA-106 lifted, changesets -[7dfa94c](http://xenbits.xen.org/gitweb/ +[7dfa94c](https://xenbits.xen.org/gitweb/ ?p=xen.git;a=commitdiff;h=7dfa94c6212b979cbfc8cff5ad5336922f4809d9), -[ecf5678](http://xenbits.xen.org/gitweb/ +[ecf5678](https://xenbits.xen.org/gitweb/ ?p=xen.git;a=commitdiff;h=ecf5678200ad2642b69ffea47ad138190bc3e190) and -[36ebf14](http://xenbits.xen.org/gitweb/ +[36ebf14](https://xenbits.xen.org/gitweb/ ?p=xen.git;a=commitdiff;h=36ebf14ebe60310aa22952cbb94de951c158437d) were the eventual bugfixes which caused Xen to inject software exceptions correctly. @@ -136,9 +136,9 @@ progressed only in the authors copious free time, when more important tasks were not being done. Moving forward by a year, the author was dismayed to discover that the -[XSA-156](http://xenbits.xen.org/xsa/advisory-156.html) release contained a +[XSA-156](https://xenbits.xen.org/xsa/advisory-156.html) release contained a regression (causing infinite loops inside guests which used hardware debugging -facilities, fixed in [0747bc8](http://xenbits.xen.org/gitweb/ +facilities, fixed in [0747bc8](https://xenbits.xen.org/gitweb/ ?p=xen.git;a=commitdiff;h=0747bc8b4d85f3fc0ee1e58418418fa0229e8ff8)) which would have been caught by the original test for XSA-106, had that test been in a usable state. diff --git a/include/xen/errno.h b/include/xen/errno.h index 148ffb7..8e4de2e 100644 --- a/include/xen/errno.h +++ b/include/xen/errno.h @@ -7,7 +7,7 @@ * * The set of identifiers to be added here shouldn't extend beyond what * POSIX mandates (see e.g. - * http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/errno.h.html) + * https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/errno.h.html) * with the exception that we support some optional (XSR) values * specified there (but no new ones should be added). */ diff --git a/make-new-test.sh b/make-new-test.sh index 2036eb6..cbfd5ed 100755 --- a/make-new-test.sh +++ b/make-new-test.sh @@ -102,7 +102,7 @@ else cat < 0 virtual boundary, whether the @@ -18,7 +18,7 @@ * used and behaves normally as a 32bit register, including in 16bit protected * mode segments, as well as in Real and Unreal mode. * - * The upstream change [0640ffb6](http://xenbits.xen.org/gitweb/ + * The upstream change [0640ffb6](https://xenbits.xen.org/gitweb/ * ?p=xen.git;a=commitdiff;h=0640ffb67fb92e2561c63b9308c27b71281fdd72) broke * this behaviour, and introduced conditions which resulted in x86 emulator * state corruption. diff --git a/tests/xsa-188/main.c b/tests/xsa-188/main.c index 697b494..207bbd9 100644 --- a/tests/xsa-188/main.c +++ b/tests/xsa-188/main.c @@ -4,7 +4,7 @@ * * @page test-xsa-188 XSA-188 * - * Advisory: [XSA-188](http://xenbits.xen.org/xsa/advisory-188.html) + * Advisory: [XSA-188](https://xenbits.xen.org/xsa/advisory-188.html) * * EVTCHNOP_init_control with an invalid control_gfn will correctly * fail and free resources but incorrectly leaves a pointer to freed diff --git a/tests/xsa-191/main.c b/tests/xsa-191/main.c index f360148..2aa48fb 100644 --- a/tests/xsa-191/main.c +++ b/tests/xsa-191/main.c @@ -4,7 +4,7 @@ * * @page test-xsa-191 XSA-191 * - * Advisory: [XSA-191](http://xenbits.xen.org/xsa/advisory-191.html) + * Advisory: [XSA-191](https://xenbits.xen.org/xsa/advisory-191.html) * * Before XSA-191, Xen had several bugs with its handling of segments which * shouldn't be eligible for use. Memory accesses through user segments and diff --git a/tests/xsa-192/main.c b/tests/xsa-192/main.c index f94fac8..1cf0f97 100644 --- a/tests/xsa-192/main.c +++ b/tests/xsa-192/main.c @@ -4,7 +4,7 @@ * * @page test-xsa-192 XSA-192 * - * Advisory: [XSA-192](http://xenbits.xen.org/xsa/advisory-192.html) + * Advisory: [XSA-192](https://xenbits.xen.org/xsa/advisory-192.html) * * Before XSA-192, a bug existed with Xen's handling of task switches into * vm86 mode, whereby LDTR got loaded with vm86 attributes. diff --git a/tests/xsa-193/main.c b/tests/xsa-193/main.c index 312f520..970d63c 100644 --- a/tests/xsa-193/main.c +++ b/tests/xsa-193/main.c @@ -4,9 +4,9 @@ * * @page test-xsa-193 XSA-193 * - * Advisory: [XSA-193](http://xenbits.xen.org/xsa/advisory-193.html) + * Advisory: [XSA-193](https://xenbits.xen.org/xsa/advisory-193.html) * - * Xen change [c42494acb2](http://xenbits.xen.org/gitweb/ + * Xen change [c42494acb2](https://xenbits.xen.org/gitweb/ * ?p=xen.git;a=commitdiff;h=c42494acb2f7f31e561d38f06c59a50ee4198f36) * switched wrmsr_safe() for wr{f,g}sbase(), neglecting to consider that they * internally may use plain wrmsr() or the `wr{f,g}sbase` instructions, both diff --git a/tests/xsa-194/main.c b/tests/xsa-194/main.c index f7e9c67..bf31a99 100644 --- a/tests/xsa-194/main.c +++ b/tests/xsa-194/main.c @@ -4,7 +4,7 @@ * * @page test-xsa-194 XSA-194 * - * Advisory: [XSA-194](http://xenbits.xen.org/xsa/advisory-194.html) + * Advisory: [XSA-194](https://xenbits.xen.org/xsa/advisory-194.html) * * When a guest requests BSD_SYMTAB, Some versions of libelf use a packed * struct containing an Elf header, and three Section headers. These headers diff --git a/tests/xsa-195/main.c b/tests/xsa-195/main.c index eba390b..a3b568c 100644 --- a/tests/xsa-195/main.c +++ b/tests/xsa-195/main.c @@ -4,7 +4,7 @@ * * @page test-xsa-195 XSA-195 * - * Advisory: [XSA-195](http://xenbits.xen.org/xsa/advisory-195.html) + * Advisory: [XSA-195](https://xenbits.xen.org/xsa/advisory-195.html) * * The `bt` family of instructions can reference an arbitrary bit offset from * their memory operand. The x86 instruction emulator accounts for this by diff --git a/tests/xsa-196/main.c b/tests/xsa-196/main.c index 0c40729..272108c 100644 --- a/tests/xsa-196/main.c +++ b/tests/xsa-196/main.c @@ -4,9 +4,9 @@ * * @page test-xsa-196 XSA-196 * - * Advisory: [XSA-196](http://xenbits.xen.org/xsa/advisory-196.html) + * Advisory: [XSA-196](https://xenbits.xen.org/xsa/advisory-196.html) * - * Xen change [36ebf14ebe](http://xenbits.xen.org/gitweb/ + * Xen change [36ebf14ebe](https://xenbits.xen.org/gitweb/ * ?p=xen.git;a=commitdiff;h=36ebf14ebe60310aa22952cbb94de951c158437d) * contained a bug when calculating the correct size of an IDT entry. * diff --git a/tests/xsa-200/main.c b/tests/xsa-200/main.c index 7973777..672abf2 100644 --- a/tests/xsa-200/main.c +++ b/tests/xsa-200/main.c @@ -4,7 +4,7 @@ * * @page test-xsa-200 XSA-200 * - * Advisory: [XSA-200](http://xenbits.xen.org/xsa/advisory-200.html) + * Advisory: [XSA-200](https://xenbits.xen.org/xsa/advisory-200.html) * * Before XSA-200, the instruction emulator in Xen had a bug where it * incorrectly honoured the legacy operand-side override prefix for diff --git a/tests/xsa-203/main.c b/tests/xsa-203/main.c index e786577..eb37568 100644 --- a/tests/xsa-203/main.c +++ b/tests/xsa-203/main.c @@ -4,7 +4,7 @@ * * @page test-xsa-203 XSA-203 * - * Advisory: [XSA-203](http://xenbits.xen.org/xsa/advisory-203.html) + * Advisory: [XSA-203](https://xenbits.xen.org/xsa/advisory-203.html) * * Versions of Xen between 4.6 (when VMFUNC support was introduced) and * XSA-203, would follow a NULL function pointer on non-Intel hardware. diff --git a/tests/xsa-204/main.c b/tests/xsa-204/main.c index ac8c3c8..a8140b0 100644 --- a/tests/xsa-204/main.c +++ b/tests/xsa-204/main.c @@ -4,7 +4,7 @@ * * @page test-xsa-204 XSA-204 * - * Advisory: [XSA-204](http://xenbits.xen.org/xsa/advisory-204.html) + * Advisory: [XSA-204](https://xenbits.xen.org/xsa/advisory-204.html) * * SYSCALL (unlike most instructions) evaluates its singlestep action based on * the resulting EFLAGS.TF, not the starting EFLAGS.TF. As the @#DB is raised diff --git a/tests/xsa-212/main.c b/tests/xsa-212/main.c index 50cc13a..f1d97a3 100644 --- a/tests/xsa-212/main.c +++ b/tests/xsa-212/main.c @@ -4,7 +4,7 @@ * * @page test-xsa-212 XSA-212 * - * Advisory: [XSA-212](http://xenbits.xen.org/xsa/advisory-212.html) + * Advisory: [XSA-212](https://xenbits.xen.org/xsa/advisory-212.html) * * The XENMEM_exchange hypercall previously had incomplete checks on the * safety of the parameters passed. XENMEM_exchange takes an input and output diff --git a/tests/xsa-213/main.c b/tests/xsa-213/main.c index d3e713b..a0c8a1b 100644 --- a/tests/xsa-213/main.c +++ b/tests/xsa-213/main.c @@ -4,7 +4,7 @@ * * @page test-xsa-213 XSA-213 * - * Advisory: [XSA-213](http://xenbits.xen.org/xsa/advisory-213.html) + * Advisory: [XSA-213](https://xenbits.xen.org/xsa/advisory-213.html) * * Before XSA-213, Xen would allow the use of __HYPERCALL_iret in a multicall. * __HYPERCALL_iret switches the guest from kernel mode into user mode, but diff --git a/tests/xsa-221/main.c b/tests/xsa-221/main.c index 824030b..4998640 100644 --- a/tests/xsa-221/main.c +++ b/tests/xsa-221/main.c @@ -4,9 +4,9 @@ * * @page test-xsa-221 XSA-221 * - * Advisory: [XSA-221](http://xenbits.xen.org/xsa/advisory-221.html) + * Advisory: [XSA-221](https://xenbits.xen.org/xsa/advisory-221.html) * - * The upstream change [fbbd5009e6](http://xenbits.xen.org/gitweb/ + * The upstream change [fbbd5009e6](https://xenbits.xen.org/gitweb/ * ?p=xen.git;a=commitdiff;h=fbbd5009e6ed1201731b1727762070c1a988e67d) * neglected to check that ports were suitably initialised before * dereferencing their structure. diff --git a/tests/xsa-224/main.c b/tests/xsa-224/main.c index d334a53..123608b 100644 --- a/tests/xsa-224/main.c +++ b/tests/xsa-224/main.c @@ -4,7 +4,7 @@ * * @page test-xsa-224 XSA-224 * - * Advisory: [XSA-224](http://xenbits.xen.org/xsa/advisory-224.html) + * Advisory: [XSA-224](https://xenbits.xen.org/xsa/advisory-224.html) * * XSA-224 has multiple CVEs assigned. This testcase exercises CVE-2017-10920 * specifically. diff --git a/tests/xsa-227/main.c b/tests/xsa-227/main.c index a32ec66..1750fc6 100644 --- a/tests/xsa-227/main.c +++ b/tests/xsa-227/main.c @@ -4,7 +4,7 @@ * * @page test-xsa-227 XSA-227 * - * Advisory: [XSA-227](http://xenbits.xen.org/xsa/advisory-xsa-227.html) + * Advisory: [XSA-227](https://xenbits.xen.org/xsa/advisory-xsa-227.html) * * For x86 PV guests, the #GNTTABOP_map_grant_ref hypercall allows mapping by * nominated linear address, or by nominating a specific L1e. However, there diff --git a/tests/xsa-231/main.c b/tests/xsa-231/main.c index 2771beb..fcc4647 100644 --- a/tests/xsa-231/main.c +++ b/tests/xsa-231/main.c @@ -4,7 +4,7 @@ * * @page test-xsa-231 XSA-231 * - * Advisory: [XSA-231](http://xenbits.xen.org/xsa/advisory-231.html) + * Advisory: [XSA-231](https://xenbits.xen.org/xsa/advisory-231.html) * * Before XSA-231, the node parameter in xen_memory_reservation was passed * unaudited into the heap allocator, which ASSERT()ed it was range, then diff --git a/tests/xsa-232/main.c b/tests/xsa-232/main.c index 2f649f9..e8eddc3 100644 --- a/tests/xsa-232/main.c +++ b/tests/xsa-232/main.c @@ -4,7 +4,7 @@ * * @page test-xsa-232 XSA-232 * - * Advisory: [XSA-232](http://xenbits.xen.org/xsa/advisory-232.html) + * Advisory: [XSA-232](https://xenbits.xen.org/xsa/advisory-232.html) * * GNTTABOP_cache_flush takes a machine address, looks up the page owner and * unconditionally follows the owners grant table pointer. For system domains diff --git a/tests/xsa-234/main.c b/tests/xsa-234/main.c index f28a7e3..2b65ef2 100644 --- a/tests/xsa-234/main.c +++ b/tests/xsa-234/main.c @@ -4,7 +4,7 @@ * * @page test-xsa-234 XSA-234 * - * Advisory: [XSA-234](http://xenbits.xen.org/xsa/advisory-234.html) + * Advisory: [XSA-234](https://xenbits.xen.org/xsa/advisory-234.html) * * Various grant unmapping operations will succeed and drop a writeable * reference count, even when the mapping was only read-only. This can be diff --git a/tests/xsa-239/main.c b/tests/xsa-239/main.c index 79f6810..0e0bb9f 100644 --- a/tests/xsa-239/main.c +++ b/tests/xsa-239/main.c @@ -4,7 +4,7 @@ * * @page test-xsa-239 XSA-239 * - * Advisory: [XSA-239](http://xenbits.xen.org/xsa/advisory-239.html) + * Advisory: [XSA-239](https://xenbits.xen.org/xsa/advisory-239.html) * * The IOAPIC REG_SELECT register is an 8bit register, which is expected to be * accessed with 32bit accesses. diff --git a/tests/xsa-255/main.c b/tests/xsa-255/main.c index 647de51..f3db629 100644 --- a/tests/xsa-255/main.c +++ b/tests/xsa-255/main.c @@ -4,7 +4,7 @@ * * @page test-xsa-255 XSA-255 * - * Advisory: [XSA-255](http://xenbits.xen.org/xsa/advisory-255.html) + * Advisory: [XSA-255](https://xenbits.xen.org/xsa/advisory-255.html) * * The Grant Table v2 API has includes a set of status frames, which the guest * is expected to map in addition to the regular grant frames. These frames diff --git a/tests/xsa-259/main.c b/tests/xsa-259/main.c index 0432c13..7ccb076 100644 --- a/tests/xsa-259/main.c +++ b/tests/xsa-259/main.c @@ -4,7 +4,7 @@ * * @page test-xsa-259 XSA-259 * - * Advisory: [XSA-259](http://xenbits.xen.org/xsa/advisory-259.html) + * Advisory: [XSA-259](https://xenbits.xen.org/xsa/advisory-259.html) * * The Meltdown mitigation work (XPTI) didn't correctly deal with an error * path connecting the `int $0x80` special case handing with general exception diff --git a/tests/xsa-260/main.c b/tests/xsa-260/main.c index 2ffd7a2..cdf5274 100644 --- a/tests/xsa-260/main.c +++ b/tests/xsa-260/main.c @@ -4,7 +4,7 @@ * * @page test-xsa-260 XSA-260 * - * Advisory: [XSA-260](http://xenbits.xen.org/xsa/advisory-260.html) + * Advisory: [XSA-260](https://xenbits.xen.org/xsa/advisory-260.html) * * The `mov` and `pop` instructions, when encoded with an @%ss destination * register, set the `movss` shadow in hardware, which prevents diff --git a/tests/xsa-261/main.c b/tests/xsa-261/main.c index 9bfaa92..524a954 100644 --- a/tests/xsa-261/main.c +++ b/tests/xsa-261/main.c @@ -4,7 +4,7 @@ * * @page test-xsa-261 XSA-261 * - * Advisory: [XSA-261](http://xenbits.xen.org/xsa/advisory-261.html) + * Advisory: [XSA-261](https://xenbits.xen.org/xsa/advisory-261.html) * * Before XSA-261, Xen didn't implement IO-APIC interrupt routing for HPET * timers properly, and attempting to configure a IRQ above the legacy PIC diff --git a/tests/xsa-265/main.c b/tests/xsa-265/main.c index 046faef..b296ea4 100644 --- a/tests/xsa-265/main.c +++ b/tests/xsa-265/main.c @@ -4,10 +4,10 @@ * * @page test-xsa-265 XSA-265 * - * Advisory: [XSA-265](http://xenbits.xen.org/xsa/advisory-264.html) + * Advisory: [XSA-265](https://xenbits.xen.org/xsa/advisory-264.html) * * One of the fixes for - * [XSA-260](http://xenbits.xen.org/gitweb/?p=xen.git;a=commitdiff;h=75d6828bc2146d0eea16adc92376951a310d94a7) + * [XSA-260](https://xenbits.xen.org/gitweb/?p=xen.git;a=commitdiff;h=75d6828bc2146d0eea16adc92376951a310d94a7) * introduced logic to try and prevent livelocks of @#DB exceptions in * hypervisor context. However, it failed to account for the fact that some * %dr6 bits are sticky and never cleared by hardware. diff --git a/tests/xsa-269/main.c b/tests/xsa-269/main.c index 581709d..d633d50 100644 --- a/tests/xsa-269/main.c +++ b/tests/xsa-269/main.c @@ -4,7 +4,7 @@ * * @page test-xsa-269 XSA-269 * - * Advisory: [XSA-269](http://xenbits.xen.org/xsa/advisory-269.html) + * Advisory: [XSA-269](https://xenbits.xen.org/xsa/advisory-269.html) * * Before XSA-269, no reserved bit checking was performed for writes to * MSR_DEBUGCTL. Branch Trace Store isn't virtualised, and must only be diff --git a/tests/xsa-277/main.c b/tests/xsa-277/main.c index 1bd06c9..78f2c12 100644 --- a/tests/xsa-277/main.c +++ b/tests/xsa-277/main.c @@ -4,7 +4,7 @@ * * @page test-xsa-277 XSA-277 * - * Advisory: [XSA-277](http://xenbits.xen.org/xsa/advisory-277.html) + * Advisory: [XSA-277](https://xenbits.xen.org/xsa/advisory-277.html) * * Before XSA-277, an error path in the P2M code left a spinlock held when the * guest tried to remove a page which was already not present. diff --git a/tests/xsa-278/main.c b/tests/xsa-278/main.c index 919654c..3c1fe4a 100644 --- a/tests/xsa-278/main.c +++ b/tests/xsa-278/main.c @@ -4,10 +4,10 @@ * * @page test-xsa-278 XSA-278 * - * Advisory: [XSA-278](http://xenbits.xen.org/xsa/advisory-278.html) + * Advisory: [XSA-278](https://xenbits.xen.org/xsa/advisory-278.html) * * Between - * [ac6a4500b](http://xenbits.xen.org/gitweb/?p=xen.git;a=commitdiff;h=ac6a4500b2bed47fa135afbf8e4caeb4b3df546d) + * [ac6a4500b](https://xenbits.xen.org/gitweb/?p=xen.git;a=commitdiff;h=ac6a4500b2bed47fa135afbf8e4caeb4b3df546d) * (Xen 4.9) and XSA-278, Xen incorrectly handled its concept of "in VMX * mode", and allowed the use of the VT-x instructions before VMXON had * completed. diff --git a/tests/xsa-279/main.c b/tests/xsa-279/main.c index c0fa604..fe13296 100644 --- a/tests/xsa-279/main.c +++ b/tests/xsa-279/main.c @@ -4,7 +4,7 @@ * * @page test-xsa-279 XSA-279 * - * Advisory: [XSA-279](http://xenbits.xen.org/xsa/advisory-279.html) + * Advisory: [XSA-279](https://xenbits.xen.org/xsa/advisory-279.html) * * When `PCID` support was added to Xen to mitigate some of the performance * hit from the Meltdown protection, Xen's internal TLB flushing changed from -- 2.39.5