From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: xen-devel <xen-devel@lists.xenproject.org>
Subject: Backports to stable
Date: Sun, 7 Oct 2018 03:04:33 +0200 [thread overview]
Message-ID: <20181007010433.GB2975@mail-itl> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2306 bytes --]
Hi,
I'd like to propose backporting GCC7/8 fixes to all stable branches. Below
is a list up to stable-4.6, but some of the patches are already on
select branches (developed during that release cycle, or already
backported). If you want, I can prepare separate lists for each branch,
but in practice `git cherry-pick` do the right thing already.
e0a97098e2 x86: fix section type mismatch in mm.c
fa7789ef18 tools/libxc: fix strncpy size
796dea37fb tools: include sys/sysmacros.h on Linux
850e89b3ef tools/blktap2: fix possible '\0' truncation
3a633c2614 tools/blktap2: fix hypothetical buffer overflow
f49fa658b5 tools:misc:xenlockprof: fix possible format string overflow
27751d8924 tools/misc: fix hypothetical buffer overflow in xen-lowmemd
ebdba150bf xenalyze: fix misleading indentation.
87761277d7 xenalyze: remove cr3_compare_total
c2a17869d5 libfsimage: replace deprecated readdir_r() with readdir()
938c8f53b1 tools/xenpmd: fix possible '\0' truncation
e75c9dc85f xenpmd: make 32 bit gcc 8.1 non-debug build work
2d78f78a14 tools: fix several "format-truncation" warnings with GCC 7
b9daff9d81 libxl: replace deprecated readdir_r() with readdir()
b021beb21a tools: libxl: NULL terminate partially constructed hex string
7f601f7c34 tools/gdbsx: fix -Wstringop-truncation warning
# This one doesn't apply cleanly, because acpi stuff moved
# tools/firmware/hvmloader/acpi -> tools/acpi
858dbaaeda libacpi: fixes for iasl >= 20180427
# Not sure if a good idea in a stable branch; if not acceptable, I can extract
# gcc-7/gcc-8 related commits and add them to tools/firmware/etherboot/patches/
461b216534 ipxe: update to newer commit
Another thing worth backporting is xs_watch thread stack size fix +
related patches:
b4f98dc0d8 tools: fix typo in tools/Rules.mk
448c03b3cb tools/xenstore: try to get minimum thread stack size for watch thread
c9bd8a7365 tools/xenstore: add libdl dependency to libxenstore
1a37319492 tools/xenstore: fix linking libxenstore with ldl
--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 157 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next reply other threads:[~2018-10-07 1:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-07 1:04 Marek Marczykowski-Górecki [this message]
2018-10-08 9:29 ` Backports to stable Jan Beulich
2018-10-08 10:40 ` Marek Marczykowski
2018-10-08 11:57 ` Jan Beulich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181007010433.GB2975@mail-itl \
--to=marmarek@invisiblethingslab.com \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.