rseq: Regression fixes for legacy/tcmalloc behaviour
cover rseq: Regression fixes for legacy/tcmalloc behaviour
Greg!
The following three patches are the stable backports for the rseq patches which rejected against 7.0.y
Thanks,
tglx
PATCH 1/3 rseq: Revert to historical performance killing behaviour
From: Thomas Gleixner <[email protected]>
commit b9eac6a9d93c952c4b7775a24d5c7a1bbf4c3c00 upstream.
The recent RSEQ optimization work broke the TCMalloc abuse of the RSEQ ABI as it not longer unconditionally updates the CPU, node, mm_cid fields, which are documented as read only for user space. Due to the observed behavior of the kernel it was possible for TCMalloc to overwrite the cpu_id_start field for their own purposes and rely on the kernel to update it unconditionally after each context switch and before signal delivery.
The RSEQ ABI only guarantees that these fields are updated when the data changes, i.e. the task is migrated or the MMCID of the task changes due to switching from or to per CPU ownership mode.
The optimization work eliminated the unconditional updates and reduced them to the documented ABI guarantees, which results in a massive performance win for syscall, scheduling heavy work loads, which in turn breaks the TCMalloc expectations.
There have been several options discussed to restore the TCMalloc functionality while preserving the optimization benefits. They all end up in a series of hard to maintain workarounds, which in the worst case introduce overhead for everyone, e.g. in the scheduler.
The requirements of TCMalloc and the optimization work are diametral and the required work arounds are a maintainence burden. They end up as fragile constructs, which are blocking further optimization work and are pretty much guaranteed to cause more subtle issues down the road.
The optimization work heavily depends on the generic entry code, which is not used by all architectures yet. So the rework preserved the original mechanism moslty unmodified to keep the support for architectures, which handle rseq in their own exit to user space loop. That code is currently optimized out by the compiler on architectures which use the generic entry code.
This allows to revert back to the original behaviour by replacing the compile time constant conditions with a runtime condition where required, which disables the optimization and the dependend time slice extension feature until the run-time condition can be enabled in the RSEQ registration code on a per task basis again.
The following changes are required to restore the original behavior, which makes TCMalloc work again:
1) Replace the compile time constant conditionals with runtime conditionals where appropriate to prevent the compiler from optimizing the legacy mode out
2) Enforce unconditional update of IDs on context switch for the non-optimized v1 mode
3) Enforce update of IDs in the pre signal delivery path for the non-optimized v1 mode
4) Enforce update of IDs in the membarrier(RSEQ) IPI for the non-optimized v1 mode
5) Make time slice and future extensions depend on optimized v2 mode
This brings back the full performance problems, but preserves the v2 optimization code and for generic entry code using architectures also the TIF_RSEQ optimization which avoids a full evaluation of the exit to user mode loop in many cases.
--- include/linux/rseq.h | 35 ++++++++++++++++++++++++----------- include/linux/rseq_entry.h | 39 +++++++++++++++++++++++++++++---------- include/linux/rseq_types.h | 9 ++++++++- kernel/rseq.c | 42 ++++++++++++++++++++++++++++++++++-------- kernel/sched/membarrier.c | 11 ++++++++++- 5 files changed, 105 insertions(+), 31 deletions(-)
---
include/linux/rseq.h +24 -11
@@ -9,6 +9,11 @@void __rseq_handle_slowpath (struct pt_regs *regs); +static __always_inline bool rseq_v2(struct task_struct *t) +{ +return IS_ENABLED (CONFIG_GENERIC_IRQ_ENTRY ) &&likely (t->rseq.event.has_rseq >1 ); +} +/* Invoked from resume_user_mode_work() */ static inline void rseq_handle_slowpath (struct pt_regs *regs) {
@@ -16,8 +21,7 @@ static inline void rseq_handle_slowpath(if (current->rseq.event.slowpath)__rseq_handle_slowpath (regs); }else { -/* '&' is intentional to spare one conditional branch */ -if (current->rseq.event.sched_switch & current->rseq.event.has_rseq) +if (current->rseq.event.sched_switch && current->rseq.event.has_rseq)__rseq_handle_slowpath (regs); } }
@@ -30,9 +34,9 @@ void __rseq_signal_deliver(int sig, stru*/ static inline void rseq_signal_deliver (struct ksignal *ksig,struct pt_regs *regs) { -if (IS_ENABLED (CONFIG_GENERIC_IRQ_ENTRY )) { -/* '&' is intentional to spare one conditional branch */ -if (current->rseq.event.has_rseq & current->rseq.event.user_irq) +if (rseq_v2 (current)) { +/* has_rseq is implied in rseq_v2() */ +if (current->rseq.event.user_irq)__rseq_signal_deliver (ksig->sig, regs); }else {if (current->rseq.event.has_rseq)
@@ -50,15 +54,22 @@ static __always_inline void rseq_sched_s {struct rseq_event *ev = &t->rseq.event; -if (IS_ENABLED (CONFIG_GENERIC_IRQ_ENTRY )) { +/* +* Only apply the user_irq optimization for RSEQ ABI V2 registrations. +* Legacy users like TCMalloc rely on the original ABI V1 behaviour +* which updates IDs on every context swtich. +*/ +if (rseq_v2 (t)) {/* -* Avoid a boat load of conditionals by using simple logic -* to determine whether NOTIFY_RESUME needs to be raised. +* Avoid a boat load of conditionals by using simple logic to +* determine whether TIF_NOTIFY_RESUME or TIF_RSEQ needs to be +* raised. * -* It's required when the CPU or MM CID has changed or -* the entry was from user space. +* It's required when the CPU or MM CID has changed or the entry +* was via interrupt from user space. ev->has_rseq does not have +* to be evaluated here because rseq_v2() implies has_rseq. */ -bool raise = (ev->user_irq | ev->ids_changed) & ev->has_rseq; +bool raise = ev->user_irq | ev->ids_changed;if (raise) { ev->sched_switch = true;
@@ -66,6 +77,7 @@ static __always_inline void rseq_sched_s } }else {if (ev->has_rseq) { + t->rseq.event.ids_changed = true; t->rseq.event.sched_switch = true;rseq_raise_notify_resume (t); }
@@ -161,6 +173,7 @@ static inline unsigned int rseq_alloc_al }#else /* CONFIG_RSEQ */ +static inline bool rseq_v2 (struct task_struct *t) {return false; }static inline void rseq_handle_slowpath (struct pt_regs *regs) { }static inline void rseq_signal_deliver (struct ksignal *ksig,struct pt_regs *regs) { }static inline void rseq_sched_switch_event (struct task_struct *t) { }
include/linux/rseq_entry.h +29 -10
@@ -110,6 +110,20 @@ static __always_inline void rseq_slice_c t->rseq.slice.state.granted = false; } +/* +* Open coded, so it can be invoked within a user access region. +* +* This clears the user space state of the time slice extensions field only when +* the task has registered the optimized RSEQ_ABI V2. Some legacy registrations, +* e.g. TCMalloc, have conflicting non-ABI fields in struct RSEQ, which would be +* overwritten by an unconditional write. +*/ +#define rseq_slice_clear_user (rseq, efault) \ +do { \ + if (rseq_slice_extension_enabled()) \ + unsafe_put_user(0U, &rseq->slice_ctrl.all, efault); \ +} while (0) + static __always_inline bool rseq_grant_slice_extension(bool work_pending) {struct task_struct *curr = current;
@@ -220,6 +234,7 @@ static __always_inline bool rseq_slice_e static __always_inline bool rseq_arm_slice_extension_timer(void) { return false; } static __always_inline void rseq_slice_clear_grant(struct task_struct *t) { } static __always_inline bool rseq_grant_slice_extension(bool work_pending) { return false; } +#define rseq_slice_clear_user (rseq, efault) do { } while (0)#endif /* !CONFIG_RSEQ_SLICE_EXTENSION */ bool rseq_debug_update_user_cs (struct task_struct *t,struct pt_regs *regs,unsigned long csaddr);
@@ -507,11 +522,9 @@ bool rseq_set_ids_get_csaddr(struct taskif (csaddr)unsafe_get_user (*csaddr, &rseq->rseq_cs, efault); -/* Open coded, so it's in the same user access region */ -if (rseq_slice_extension_enabled ()) { -/* Unconditionally clear it, no point in conditionals */ -unsafe_put_user (0U , &rseq->slice_ctrl.all, efault); - } +/* RSEQ ABI V2 only operations */ +if (rseq_v2 (t)) +rseq_slice_clear_user (rseq, efault); }rseq_slice_clear_grant (t);
@@ -602,6 +615,14 @@ static __always_inline bool rseq_exit_us* interrupts disabled */ guard (pagefault)(); +/* +* This optimization is only valid when the task registered for the +* optimized RSEQ_ABI_V2 variant. Some legacy users rely on the original +* RSEQ implementation behaviour which unconditionally updated the IDs. +* rseq_sched_switch_event() ensures that legacy registrations always +* have both sched_switch and ids_changed set, which is compatible with +* the historical TIF_NOTIFY_RESUME behaviour. +*/ if (likely (!t->rseq.event.ids_changed)) {struct rseq __user *rseq = t->rseq.usrptr;/*
@@ -613,11 +634,9 @@ static __always_inline bool rseq_exit_us scoped_user_rw_access(rseq, efault) {unsafe_get_user (csaddr, &rseq->rseq_cs, efault); -/* Open coded, so it's in the same user access region */ -if (rseq_slice_extension_enabled ()) { -/* Unconditionally clear it, no point in conditionals */ -unsafe_put_user (0U , &rseq->slice_ctrl.all, efault); - } +/* RSEQ ABI V2 only operations */ +if (rseq_v2 (t)) +rseq_slice_clear_user (rseq, efault); }rseq_slice_clear_grant (t);
include/linux/rseq_types.h +8 -1
@@ -9,6 +9,12 @@#ifdef CONFIG_RSEQ struct rseq ; +/* +* rseq_event::has_rseq contains the ABI version number so preserving it +* in AND operations requires a mask. +*/ +#define RSEQ_HAS_RSEQ_VERSION_MASK 0xff +/** * struct rseq_event - Storage for rseq related event management * @all: Compound to initialize and clear the data efficiently
@@ -17,7 +23,8 @@ struct rseq;* exit to user * @ids_changed: Indicator that IDs need to be updated * @user_irq: True on interrupt entry from user mode -* @has_rseq: True if the task has a rseq pointer installed +* @has_rseq: Greater than 0 if the task has a rseq pointer installed. +* Contains the RSEQ version number * @error: Compound error code for the slow path to analyze * @fatal: User space data corrupted or invalid * @slowpath: Indicator that slow path processing via TIF_NOTIFY_RESUME
kernel/rseq.c +34 -8
85 lines not on this page · raw message
kernel/sched/membarrier.c +10 -1
@@ -199,7 +199,16 @@ static void ipi_rseq(void *info)* is negligible. */ smp_mb (); -rseq_sched_switch_event (current); +/* +* Legacy mode requires that IDs are written and the critical section is +* evaluated. V2 optimized mode handles the critical section and IDs are +* only updated if they change as a consequence of preemption after +* return from this IPI. +*/ +if (rseq_v2 (current)) +rseq_sched_switch_event (current); +else +rseq_force_update (); }static void ipi_sync_rq_state (void *info)
PATCH 2/3 rseq: Implement read only ABI enforcement for optimized RSEQ V2 mode
In reply to Thomas GleixnerFrom: Thomas Gleixner <[email protected]>
commit 82f572449cfe75f12ea985986da60e11f308f77d upstream.
The optimized RSEQ V2 mode requires that user space adheres to the ABI specification and does not modify the read-only fields cpu_id_start, cpu_id, node_id and mm_cid behind the kernel's back.
While the kernel does not rely on these fields, the adherence to this is a fundamental prerequisite to allow multiple entities, e.g. libraries, in an application to utilize the full potential of RSEQ without stepping on each other toes.
Validate this adherence on every update of these fields. If the kernel detects that user space modified the fields, the application is force terminated.
--- include/linux/rseq_entry.h | 83 ++++++++++++++++----------------------------- include/linux/rseq_types.h | 4 +- kernel/rseq.c | 5 +- 3 files changed, 35 insertions(+), 57 deletions(-)
---
include/linux/rseq_entry.h +30 -53
@@ -238,7 +238,6 @@ static __always_inline bool rseq_grant_s#endif /* !CONFIG_RSEQ_SLICE_EXTENSION */ bool rseq_debug_update_user_cs (struct task_struct *t,struct pt_regs *regs,unsigned long csaddr); -bool rseq_debug_validate_ids (struct task_struct *t); static __always_inline void rseq_note_user_irq_entry(void) {
@@ -358,43 +357,6 @@ bool rseq_debug_update_user_cs(struct ta return false; } -/* -* On debug kernels validate that user space did not mess with it if the -* debug branch is enabled. -*/ -bool rseq_debug_validate_ids (struct task_struct *t) -{ -struct rseq __user *rseq = t->rseq.usrptr; -u32 cpu_id, uval, node_id; - -/* -* On the first exit after registering the rseq region CPU ID is -* RSEQ_CPU_ID_UNINITIALIZED and node_id in user space is 0! -*/ - node_id = t->rseq.ids.cpu_id !=RSEQ_CPU_ID_UNINITIALIZED ? -cpu_to_node (t->rseq.ids.cpu_id) :0 ; - - scoped_user_read_access(rseq, efault) { -unsafe_get_user (cpu_id, &rseq->cpu_id_start, efault); -if (cpu_id != t->rseq.ids.cpu_id) - goto die; -unsafe_get_user (uval, &rseq->cpu_id, efault); -if (uval != cpu_id) - goto die; -unsafe_get_user (uval, &rseq->node_id, efault); -if (uval != node_id) - goto die; -unsafe_get_user (uval, &rseq->mm_cid, efault); -if (uval != t->rseq.ids.mm_cid) - goto die; - } -return true; -die: - t->rseq.event.fatal = true; -efault: -return false; -} -#endif /* RSEQ_BUILD_SLOW_PATH */ /*
@@ -504,20 +466,32 @@ rseq_update_user_cs(struct task_struct ** faults in task context are fatal too. */ static rseq_inline -bool rseq_set_ids_get_csaddr(struct task_struct *t, struct rseq_ids *ids, -u32 node_id,u64 *csaddr) +bool rseq_set_ids_get_csaddr(struct task_struct *t, struct rseq_ids *ids, u64 *csaddr) {struct rseq __user *rseq = t->rseq.usrptr; -if (static_branch_unlikely (&rseq_debug_enabled)) { -if (!rseq_debug_validate_ids (t)) -return false; - } - scoped_user_rw_access(rseq, efault) { +/* Validate the R/O fields for debug and optimized mode */ +if (static_branch_unlikely (&rseq_debug_enabled) ||rseq_v2 (t)) { +u32 cpu_id, uval; + +unsafe_get_user (cpu_id, &rseq->cpu_id_start, efault); +if (cpu_id != t->rseq.ids.cpu_id) + goto die; +unsafe_get_user (uval, &rseq->cpu_id, efault); +if (uval != cpu_id) + goto die; +unsafe_get_user (uval, &rseq->node_id, efault); +if (uval != t->rseq.ids.node_id) + goto die; +unsafe_get_user (uval, &rseq->mm_cid, efault); +if (uval != t->rseq.ids.mm_cid) + goto die; + } +unsafe_put_user (ids->cpu_id, &rseq->cpu_id_start, efault);unsafe_put_user (ids->cpu_id, &rseq->cpu_id, efault); -unsafe_put_user (node_id, &rseq->node_id, efault); +unsafe_put_user (ids->node_id, &rseq->node_id, efault);unsafe_put_user (ids->mm_cid, &rseq->mm_cid, efault);if (csaddr)unsafe_get_user (*csaddr, &rseq->rseq_cs, efault);
@@ -529,10 +503,13 @@ bool rseq_set_ids_get_csaddr(struct taskrseq_slice_clear_grant (t);/* Cache the new values */ - t->rseq.ids.cpu_cid = ids->cpu_cid; + t->rseq.ids = *ids;rseq_stat_inc (rseq_stats.ids);rseq_trace_update (t, ids);return true; + +die: + t->rseq.event.fatal = true; efault:return false; }
@@ -542,11 +519,11 @@ bool rseq_set_ids_get_csaddr(struct task* is in a critical section. */ static rseq_inline bool rseq_update_usr(struct task_struct *t, struct pt_regs *regs, -struct rseq_ids *ids,u32 node_id) +struct rseq_ids *ids) {u64 csaddr; -if (!rseq_set_ids_get_csaddr (t, ids, node_id, &csaddr)) +if (!rseq_set_ids_get_csaddr (t, ids, &csaddr))return false;/*
@@ -649,12 +626,12 @@ static __always_inline bool rseq_exit_us }struct rseq_ids ids = { - .cpu_id =task_cpu (t), - .mm_cid =task_mm_cid (t), + .cpu_id =task_cpu (t), + .mm_cid =task_mm_cid (t), + .node_id =cpu_to_node (ids.cpu_id), }; -u32 node_id =cpu_to_node (ids.cpu_id); -return rseq_update_usr (t, regs, &ids, node_id); +return rseq_update_usr (t, regs, &ids); efault:return false; }
include/linux/rseq_types.h +3 -1
@@ -66,8 +66,9 @@ struct rseq_event {* compiler emit a single compare on 64-bit * @cpu_id: The CPU ID which was written last to user space * @mm_cid: The MM CID which was written last to user space +* @node_id: The node ID which was written last to user space * -* @cpu_id and @mm_cid are updated when the data is written to user space. +* @cpu_id, @mm_cid and @node_id are updated when the data is written to user space. */ struct rseq_ids { union {
@@ -77,6 +78,7 @@ struct rseq_ids {u32 mm_cid; }; }; +u32 node_id; };/**
kernel/rseq.c +2 -3
@@ -263,7 +263,6 @@ static void rseq_slowpath_update_usr(str };struct task_struct *t = current;struct rseq_ids ids; -u32 node_id;bool event;if (unlikely (t->flags &PF_EXITING ))
@@ -299,9 +298,9 @@ static void rseq_slowpath_update_usr(strif (!event)return ; - node_id =cpu_to_node (ids.cpu_id); + ids.node_id =cpu_to_node (ids.cpu_id); -if (unlikely (!rseq_update_usr (t, regs, &ids, node_id))) { +if (unlikely (!rseq_update_usr (t, regs, &ids))) {/* * Clear the errors just in case this might survive magically, but * leave the rest intact.
PATCH 3/3 rseq: Reenable performance optimizations conditionally
In reply to Thomas GleixnerFrom: Thomas Gleixner <[email protected]>
commit 99428157dcf32fdac97355aa1cc1364dbc9e073c upstream.
Due to the incompatibility with TCMalloc the RSEQ optimizations and extended features (time slice extensions) have been disabled and made run-time conditional.
The original RSEQ implementation, which TCMalloc depends on, registers a 32 byte region (ORIG_RSEG_SIZE). This region has a 32 byte alignment requirement.
The extension safe newer variant exposes the kernel RSEQ feature size via getauxval(AT_RSEQ_FEATURE_SIZE) and the alignment requirement via getauxval(AT_RSEQ_ALIGN). The alignment requirement is that the registered RSEQ region is aligned to the next power of two of the feature size. The kernel currently has a feature size of 33 bytes, which means the alignment requirement is 64 bytes.
The TCMalloc RSEQ region is embedded into a cache line aligned data structure starting at offset 32 bytes so that bytes 28-31 and the cpu_id_start field at bytes 32-35 form a 64-bit little endian pointer with the top-most bit (63 set) to check whether the kernel has overwritten cpu_id_start with an actual CPU id value, which is guaranteed to not have the top most bit set.
As this is part of their performance tuned magic, it's a pretty safe assumption, that TCMalloc won't use a larger RSEQ size.
This allows the kernel to declare that registrations with a size greater than the original size of 32 bytes, which is the cases since time slice extensions got introduced, as RSEQ ABI v2 with the following differences to the original behaviour:
1) Unconditional updates of the user read only fields (CPU, node, MMCID) are removed. Those fields are only updated on registration, task migration and MMCID changes.
2) Unconditional evaluation of the criticial section pointer is removed. It's only evaluated when user space was interrupted and was scheduled out or before delivering a signal in the interrupted context.
3) The read/only requirement of the ID fields is enforced. When the kernel detects that userspace manipulated the fields, the process is terminated. This ensures that multiple entities (libraries) can utilize RSEQ without interfering.
4) Todays extended RSEQ feature (time slice extensions) and future extensions are only enabled in the v2 enabled mode.
Registrations with the original size of 32 bytes operate in backwards compatible legacy mode without performance improvements and extended features.
Unfortunately that also affects users of older GLIBC versions which register the original size of 32 bytes and do not evaluate the kernel required size in the auxiliary vector AT_RSEQ_FEATURE_SIZE.
That's the result of the lack of enforcement in the original implementation and the unwillingness of a single entity to cooperate with the larger ecosystem for many years.
Implement the required registration changes by restructuring the spaghetti code and adding the size/version check. Also add documentation about the differences of legacy and optimized RSEQ V2 mode.
Thanks to Mathieu for pointing out the ORIG_RSEQ_SIZE constraints!
--- Documentation/userspace-api/rseq.rst | 94 +++++++++++++++++++++++- kernel/rseq.c | 144 +++++++++++++++++++++--------------- 2 files changed, 178 insertions(+), 60 deletions(-)
---
Documentation/userspace-api/rseq.rst +93 -1
@@ -24,6 +24,97 @@ Quick access to CPU number, node ID Allows to implement per CPU data efficiently. Documentation is in code and selftests. :( +Optimized RSEQ V2 +----------------- + +On architectures which utilize the generic entry code and generic TIF bits +the kernel supports runtime optimizations for RSEQ, which also enable +enhanced features like scheduler time slice extensions. + +To enable them a task has to register the RSEQ region with at least the +length advertised by getauxval(AT_RSEQ_FEATURE_SIZE). + +If existing binaries register with RSEQ_ORIG_SIZE (32 bytes), the kernel +keeps the legacy low performance mode enabled to fulfil the expectations +of existing users regarding the original RSEQ implementation behaviour. + +The following table documents the ABI and behavioral guarantees of the +legacy and the optimized V2 mode. + +.. list-table:: RSEQ modes + :header-rows: 1 + + * - Nr + - What + + - Legacy + - Optimized V2 + + * - 1 + - The cpu_id_start, cpu_id, node_id and mm_cid fields (User mode read + only) + .. Legacy + - Updated by the kernel unconditionally after each context switch and + before signal delivery + .. Optimized V2 + - Updated by the kernel if and only if they change, i.e. if the task + is migrated or mm_cid changes + + * - 2 + - The rseq_cs critical section field + .. Legacy + - Evaluated and handled unconditionally after each context switch and + before signal delivery + .. Optimized V2 + - Evaluated and handled conditionally only when user space was + interrupted and was scheduled out or before delivering a signal in + the interrupted context. + + * - 3 + - Read only fields + .. Legacy + - No strict enforcement except in debug mode + .. Optimized V2 + - Strict enforcement + + * - 4 + - membarrier(...RSEQ) + .. Legacy + - All running threads of the process are interrupted and the ID fields + are rewritten and eventually active critical sections are aborted + before they return to user space. All threads which are scheduled + out whether voluntary or not are covered by #1/#2 above. + .. Optimized V2 + - All running threads of the process are interrupted and eventually + active critical sections are aborted before these threads return to + user space. The ID fields are only updated if changed as a + consequence of the interrupt. All threads which are scheduled out + whether voluntary or not are covered by #1/#2 above. + + * - 5 + - Time slice extensions + .. Legacy + - Not supported + .. Optimized V2 + - Supported + +The legacy mode is obviously less performant as it does unconditional +updates and critical section checks even if not strictly required by the +ABI contract. That can't be changed anymore as some users depend on that +observed behavior, which in turn enables them to violate the ABI and +overwrite the cpu_id_start field for their own purposes. This is obviously +discouraged as it renders RSEQ incompatible with the intended usage and +breaks the expectation of other libraries in the same application. + +The ABI compliant optimized v2 mode, which respects the read only fields, +does not require unconditional updates and therefore is way more +performant. The kernel validates the read only fields for compliance. If +user space modifies them, the process is killed. Compliant usage allows +multiple libraries in the same application to benefit from the RSEQ +functionality without disturbing each other. The ABI compliant optimized v2 +mode also enables extended RSEQ features like time slice extensions. + + Scheduler time slice extensions -------------------------------
@@ -37,7 +128,8 @@ The prerequisites for this functionality are: * Enabled at boot time (default is enabled) - * A rseq userspace pointer has been registered for the thread + * A rseq userspace pointer has been registered for the thread in + optimized V2 mode The thread has to enable the functionality via prctl(2)::
kernel/rseq.c +85 -59
172 lines not on this page · raw message
Quoted 2 lines · Thomas Gleixner
The following three patches are the stable backports for the rseq patches which rejected against 7.0.y
Queued all three for 7.0.y, thanks.
--
Thanks,
Sasha