Linaro-mm-sig

linaro-mm-sig@lists.linaro.org

79 participants
6550 discussions

by Chong Criston

2 months

[PATCH] dma-buf/dma_fence_array: remove unused functionality

by Christian König

Amdgpu was the only user of the signal on any feature and we dropped that use case recently, so we can remove that functionality again. This allows to simplfy the dma_fence_array code a lot and saves us from the need to install a callback on all fences at the same time. Signed-off-by: Christian König <christian.koenig(a)amd.com> --- drivers/dma-buf/dma-fence-array.c | 133 +++++++----------- drivers/dma-buf/dma-fence-unwrap.c | 3 +- drivers/dma-buf/dma-resv.c | 3 +- drivers/dma-buf/st-dma-fence-unwrap.c | 2 +- .../gpu/drm/i915/gem/i915_gem_execbuffer.c | 3 +- drivers/gpu/drm/xe/xe_sync.c | 2 +- drivers/gpu/drm/xe/xe_vm.c | 4 +- include/linux/dma-fence-array.h | 28 +--- 8 files changed, 63 insertions(+), 115 deletions(-) diff --git a/drivers/dma-buf/dma-fence-array.c b/drivers/dma-buf/dma-fence-array.c index 089f69469524..0d54bf2e47ba 100644 --- a/drivers/dma-buf/dma-fence-array.c +++ b/drivers/dma-buf/dma-fence-array.c @@ -42,97 +42,71 @@ static void dma_fence_array_clear_pending_error(struct dma_fence_array *array) cmpxchg(&array->base.error, PENDING_ERROR, 0); } -static void irq_dma_fence_array_work(struct irq_work *wrk) +static void dma_fence_array_cb_func(struct dma_fence *f, + struct dma_fence_cb *cb) { - struct dma_fence_array *array = container_of(wrk, typeof(*array), work); + struct dma_fence_array *array = + container_of(cb, struct dma_fence_array, callback); - dma_fence_array_clear_pending_error(array); - - dma_fence_signal(&array->base); - dma_fence_put(&array->base); + irq_work_queue(&array->work); } -static void dma_fence_array_cb_func(struct dma_fence *f, - struct dma_fence_cb *cb) +static void irq_dma_fence_array_work(struct irq_work *wrk) { - struct dma_fence_array_cb *array_cb = - container_of(cb, struct dma_fence_array_cb, cb); - struct dma_fence_array *array = array_cb->array; + struct dma_fence_array *array = container_of(wrk, typeof(*array), work); - dma_fence_array_set_pending_error(array, f->error); + while (array->num_pending--) { + struct dma_fence *f = array->fences[array->num_pending]; - if (atomic_dec_and_test(&array->num_pending)) - irq_work_queue(&array->work); - else - dma_fence_put(&array->base); + if (!dma_fence_add_callback(f, &array->callback, + dma_fence_array_cb_func)) + return; + + dma_fence_array_set_pending_error(array, f->error); + } + + dma_fence_signal(&array->base); + dma_fence_put(&array->base); } static bool dma_fence_array_enable_signaling(struct dma_fence *fence) { struct dma_fence_array *array = to_dma_fence_array(fence); - struct dma_fence_array_cb *cb = array->callbacks; - unsigned i; - - for (i = 0; i < array->num_fences; ++i) { - cb[i].array = array; - /* - * As we may report that the fence is signaled before all - * callbacks are complete, we need to take an additional - * reference count on the array so that we do not free it too - * early. The core fence handling will only hold the reference - * until we signal the array as complete (but that is now - * insufficient). - */ - dma_fence_get(&array->base); - if (dma_fence_add_callback(array->fences[i], &cb[i].cb, - dma_fence_array_cb_func)) { - int error = array->fences[i]->error; - - dma_fence_array_set_pending_error(array, error); - dma_fence_put(&array->base); - if (atomic_dec_and_test(&array->num_pending)) { - dma_fence_array_clear_pending_error(array); - return false; - } - } - } + /* + * As we may report that the fence is signaled before all + * callbacks are complete, we need to take an additional + * reference count on the array so that we do not free it too + * early. The core fence handling will only hold the reference + * until we signal the array as complete (but that is now + * insufficient). + */ + dma_fence_get(&array->base); + irq_dma_fence_array_work(&array->work); return true; } static bool dma_fence_array_signaled(struct dma_fence *fence) { struct dma_fence_array *array = to_dma_fence_array(fence); - int num_pending; + int num_pending, error = 0; unsigned int i; /* - * We need to read num_pending before checking the enable_signal bit - * to avoid racing with the enable_signaling() implementation, which - * might decrement the counter, and cause a partial check. - * atomic_read_acquire() pairs with atomic_dec_and_test() in - * dma_fence_array_enable_signaling() - * - * The !--num_pending check is here to account for the any_signaled case - * if we race with enable_signaling(), that means the !num_pending check - * in the is_signalling_enabled branch might be outdated (num_pending - * might have been decremented), but that's fine. The user will get the - * right value when testing again later. + * Reading num_pending is just an optimization, it is perfectly + * acceptable to have a stale value for it. */ - num_pending = atomic_read_acquire(&array->num_pending); - if (test_bit(DMA_FENCE_FLAG_ENABLE_SIGNAL_BIT, &array->base.flags)) { - if (num_pending <= 0) - goto signal; - return false; - } + num_pending = READ_ONCE(array->num_pending); + for (i = 0; i < num_pending; ++i) { + struct dma_fence *f = array->fences[i]; - for (i = 0; i < array->num_fences; ++i) { - if (dma_fence_is_signaled(array->fences[i]) && !--num_pending) - goto signal; - } - return false; + if (!dma_fence_is_signaled(f)) + return false; -signal: + if (!error) + error = f->error; + } + dma_fence_array_set_pending_error(array, error); dma_fence_array_clear_pending_error(array); return true; } @@ -171,15 +145,12 @@ EXPORT_SYMBOL(dma_fence_array_ops); /** * dma_fence_array_alloc - Allocate a custom fence array - * @num_fences: [in] number of fences to add in the array * * Return dma fence array on success, NULL on failure */ -struct dma_fence_array *dma_fence_array_alloc(int num_fences) +struct dma_fence_array *dma_fence_array_alloc(void) { - struct dma_fence_array *array; - - return kzalloc_flex(*array, callbacks, num_fences); + return kzalloc_obj(struct dma_fence_array); } EXPORT_SYMBOL(dma_fence_array_alloc); @@ -190,21 +161,22 @@ EXPORT_SYMBOL(dma_fence_array_alloc); * @fences: [in] array containing the fences * @context: [in] fence context to use * @seqno: [in] sequence number to use - * @signal_on_any: [in] signal on any fence in the array * * Implementation of @dma_fence_array_create without allocation. Useful to init * a preallocated dma fence array in the path of reclaim or dma fence signaling. */ void dma_fence_array_init(struct dma_fence_array *array, int num_fences, struct dma_fence **fences, - u64 context, unsigned seqno, - bool signal_on_any) + u64 context, unsigned seqno) { static struct lock_class_key dma_fence_array_lock_key; WARN_ON(!num_fences || !fences); array->num_fences = num_fences; + array->num_pending = num_fences; + array->fences = fences; + array->base.error = PENDING_ERROR; dma_fence_init(&array->base, &dma_fence_array_ops, NULL, context, seqno); @@ -222,11 +194,6 @@ void dma_fence_array_init(struct dma_fence_array *array, */ lockdep_set_class(&array->base.inline_lock, &dma_fence_array_lock_key); - atomic_set(&array->num_pending, signal_on_any ? 1 : num_fences); - array->fences = fences; - - array->base.error = PENDING_ERROR; - /* * dma_fence_array objects should never contain any other fence * containers or otherwise we run into recursion and potential kernel @@ -249,7 +216,6 @@ EXPORT_SYMBOL(dma_fence_array_init); * @fences: [in] array containing the fences * @context: [in] fence context to use * @seqno: [in] sequence number to use - * @signal_on_any: [in] signal on any fence in the array * * Allocate a dma_fence_array object and initialize the base fence with * dma_fence_init(). @@ -264,17 +230,16 @@ EXPORT_SYMBOL(dma_fence_array_init); */ struct dma_fence_array *dma_fence_array_create(int num_fences, struct dma_fence **fences, - u64 context, unsigned seqno, - bool signal_on_any) + u64 context, unsigned seqno) { struct dma_fence_array *array; - array = dma_fence_array_alloc(num_fences); + array = dma_fence_array_alloc(); if (!array) return NULL; dma_fence_array_init(array, num_fences, fences, - context, seqno, signal_on_any); + context, seqno); return array; } diff --git a/drivers/dma-buf/dma-fence-unwrap.c b/drivers/dma-buf/dma-fence-unwrap.c index 07fe9bf45aea..53bb40e70b27 100644 --- a/drivers/dma-buf/dma-fence-unwrap.c +++ b/drivers/dma-buf/dma-fence-unwrap.c @@ -180,8 +180,7 @@ struct dma_fence *__dma_fence_unwrap_merge(unsigned int num_fences, if (count > 1) { result = dma_fence_array_create(count, array, - dma_fence_context_alloc(1), - 1, false); + dma_fence_context_alloc(1), 1); if (!result) { for (i = 0; i < count; i++) dma_fence_put(array[i]); diff --git a/drivers/dma-buf/dma-resv.c b/drivers/dma-buf/dma-resv.c index ce9e6c04897f..39a92d9f2413 100644 --- a/drivers/dma-buf/dma-resv.c +++ b/drivers/dma-buf/dma-resv.c @@ -648,8 +648,7 @@ int dma_resv_get_singleton(struct dma_resv *obj, enum dma_resv_usage usage, } array = dma_fence_array_create(count, fences, - dma_fence_context_alloc(1), - 1, false); + dma_fence_context_alloc(1), 1); if (!array) { while (count--) dma_fence_put(fences[count]); diff --git a/drivers/dma-buf/st-dma-fence-unwrap.c b/drivers/dma-buf/st-dma-fence-unwrap.c index 9c74195f47fd..45413666970e 100644 --- a/drivers/dma-buf/st-dma-fence-unwrap.c +++ b/drivers/dma-buf/st-dma-fence-unwrap.c @@ -65,7 +65,7 @@ static struct dma_fence *mock_array(unsigned int num_fences, ...) array = dma_fence_array_create(num_fences, fences, dma_fence_context_alloc(1), - 1, false); + 1); if (!array) goto error_free; return &array->base; diff --git a/drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c b/drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c index e7918f896a26..1ac91a46d87f 100644 --- a/drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c +++ b/drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c @@ -3203,8 +3203,7 @@ eb_composite_fence_create(struct i915_execbuffer *eb, int out_fence_fd) fence_array = dma_fence_array_create(eb->num_batches, fences, eb->context->parallel.fence_context, - eb->context->parallel.seqno++, - false); + eb->context->parallel.seqno++); if (!fence_array) { kfree(fences); return ERR_PTR(-ENOMEM); diff --git a/drivers/gpu/drm/xe/xe_sync.c b/drivers/gpu/drm/xe/xe_sync.c index 24d6d9af20d6..37866768d64c 100644 --- a/drivers/gpu/drm/xe/xe_sync.c +++ b/drivers/gpu/drm/xe/xe_sync.c @@ -376,7 +376,7 @@ xe_sync_in_fence_get(struct xe_sync_entry *sync, int num_sync, xe_assert(vm->xe, current_fence == num_fence); cf = dma_fence_array_create(num_fence, fences, dma_fence_context_alloc(1), - 1, false); + 1); if (!cf) goto err_out; diff --git a/drivers/gpu/drm/xe/xe_vm.c b/drivers/gpu/drm/xe/xe_vm.c index 548b0769b3ef..b916a9d90104 100644 --- a/drivers/gpu/drm/xe/xe_vm.c +++ b/drivers/gpu/drm/xe/xe_vm.c @@ -3196,7 +3196,7 @@ static struct dma_fence *ops_execute(struct xe_vm *vm, goto err_trace; } - cf = dma_fence_array_alloc(n_fence); + cf = dma_fence_array_alloc(); if (!cf) { fence = ERR_PTR(-ENOMEM); goto err_out; @@ -3240,7 +3240,7 @@ static struct dma_fence *ops_execute(struct xe_vm *vm, xe_assert(vm->xe, current_fence == n_fence); dma_fence_array_init(cf, n_fence, fences, dma_fence_context_alloc(1), - 1, false); + 1); fence = &cf->base; for_each_tile(tile, vm->xe, id) { diff --git a/include/linux/dma-fence-array.h b/include/linux/dma-fence-array.h index 370b3d2bba37..3ee55c0e2fa4 100644 --- a/include/linux/dma-fence-array.h +++ b/include/linux/dma-fence-array.h @@ -15,16 +15,6 @@ #include <linux/dma-fence.h> #include <linux/irq_work.h> -/** - * struct dma_fence_array_cb - callback helper for fence array - * @cb: fence callback structure for signaling - * @array: reference to the parent fence array object - */ -struct dma_fence_array_cb { - struct dma_fence_cb cb; - struct dma_fence_array *array; -}; - /** * struct dma_fence_array - fence to represent an array of fences * @base: fence base class @@ -33,18 +23,17 @@ struct dma_fence_array_cb { * @num_pending: fences in the array still pending * @fences: array of the fences * @work: internal irq_work function - * @callbacks: array of callback helpers + * @callback: callback structure for signaling */ struct dma_fence_array { struct dma_fence base; - unsigned num_fences; - atomic_t num_pending; + unsigned int num_fences; + unsigned int num_pending; struct dma_fence **fences; struct irq_work work; - - struct dma_fence_array_cb callbacks[] __counted_by(num_fences); + struct dma_fence_cb callback; }; /** @@ -78,16 +67,13 @@ to_dma_fence_array(struct dma_fence *fence) for (index = 0, fence = dma_fence_array_first(head); fence; \ ++(index), fence = dma_fence_array_next(head, index)) -struct dma_fence_array *dma_fence_array_alloc(int num_fences); +struct dma_fence_array *dma_fence_array_alloc(void); void dma_fence_array_init(struct dma_fence_array *array, int num_fences, struct dma_fence **fences, - u64 context, unsigned seqno, - bool signal_on_any); - + u64 context, unsigned seqno); struct dma_fence_array *dma_fence_array_create(int num_fences, struct dma_fence **fences, - u64 context, unsigned seqno, - bool signal_on_any); + u64 context, unsigned seqno); bool dma_fence_match_context(struct dma_fence *fence, u64 context); -- 2.43.0

2 months

[PATCH] dma-buf/dma_fence: be more defensive in dma_fence_release

by Christian König

In case of a refcounting bug dma_fence_release() can be called before the fence was even signaled. Previously the dma_fence framework then force signaled the fence to make sure to unblock waiters, but that can potentially lead to random memory corruption when the DMA operation continues. So be more defensive here and pick the lesser evil. Instead of force signaling the fence set an error code on the fence, re-initialize the refcount to something large and taint the kernel. This will leak memory and eventually can cause a deadlock when the fence is never signaled, but at least we won't run into an use after free or random memory corruption. Signed-off-by: Christian König <christian.koenig(a)amd.com> --- drivers/dma-buf/dma-fence.c | 18 ++++++++++++++---- 1 file changed, 14 insertions(+), 4 deletions(-) diff --git a/drivers/dma-buf/dma-fence.c b/drivers/dma-buf/dma-fence.c index 1826ba73094c..8bf07685a053 100644 --- a/drivers/dma-buf/dma-fence.c +++ b/drivers/dma-buf/dma-fence.c @@ -593,14 +593,24 @@ void dma_fence_release(struct kref *kref) /* * Failed to signal before release, likely a refcounting issue. * - * This should never happen, but if it does make sure that we - * don't leave chains dangling. We set the error flag first - * so that the callbacks know this signal is due to an error. + * This should never happen, but if try to be defensive and take + * the lesser evil. Initialize the refcount to something large, + * but not so large that it can overflow. + * + * That will leak memory and could deadlock if the fence never + * signals, but at least it doesn't cause an use after free or + * random memory corruption. + * + * Also taint the kernel to note that it is rather unreliable to + * continue. */ dma_fence_lock_irqsave(fence, flags); fence->error = -EDEADLK; - dma_fence_signal_locked(fence); + refcount_set(&fence->refcount.refcount, INT_MAX); dma_fence_unlock_irqrestore(fence, flags); + rcu_read_unlock(); + add_taint(TAINT_SOFTLOCKUP, LOCKDEP_STILL_OK); + return; } ops = rcu_dereference(fence->ops); -- 2.43.0

2 months

[PATCH 00/15] tracepoint: Avoid double static_branch evaluation at guarded call sites

by Vineeth Pillai (Google)

When a caller already guards a tracepoint with an explicit enabled check: if (trace_foo_enabled() && cond) trace_foo(args); trace_foo() internally re-evaluates the static_branch_unlikely() key. Since static branches are patched binary instructions the compiler cannot fold the two evaluations, so every such site pays the cost twice. This series introduces trace_invoke_##name() as a companion to trace_##name(). It calls __do_trace_##name() directly, bypassing the redundant static-branch re-check, while preserving all other correctness properties of the normal path (RCU-watching assertion, might_fault() for syscall tracepoints). The internal __do_trace_##name() symbol is not leaked to call sites; trace_invoke_##name() is the only new public API. if (trace_foo_enabled() && cond) trace_invoke_foo(args); /* calls __do_trace_foo() directly */ The first patch adds the three-location change to include/linux/tracepoint.h (__DECLARE_TRACE, __DECLARE_TRACE_SYSCALL, and the !TRACEPOINTS_ENABLED stub). The remaining 14 patches mechanically convert all guarded call sites found in the tree: kernel/, io_uring/, net/, accel/habanalabs, cpufreq/, devfreq/, dma-buf/, fsi/, drm/, HID, i2c/, spi/, scsi/ufs/, and btrfs/. This series is motivated by Peter Zijlstra's observation in the discussion around Dmitry Ilvokhin's locking tracepoint instrumentation series, where he noted that compilers cannot optimize static branches and that guarded call sites end up evaluating the static branch twice for no reason, and by Steven Rostedt's suggestion to add a proper API instead of exposing internal implementation details like __do_trace_##name() directly to call sites: https://lore.kernel.org/linux-trace-kernel/8298e098d3418cb446ef396f119edac5… Suggested-by: Steven Rostedt <rostedt(a)goodmis.org> Suggested-by: Peter Zijlstra <peterz(a)infradead.org> Vineeth Pillai (Google) (15): tracepoint: Add trace_invoke_##name() API kernel: Use trace_invoke_##name() at guarded tracepoint call sites io_uring: Use trace_invoke_##name() at guarded tracepoint call sites net: Use trace_invoke_##name() at guarded tracepoint call sites accel/habanalabs: Use trace_invoke_##name() at guarded tracepoint call sites cpufreq: Use trace_invoke_##name() at guarded tracepoint call sites devfreq: Use trace_invoke_##name() at guarded tracepoint call sites dma-buf: Use trace_invoke_##name() at guarded tracepoint call sites fsi: Use trace_invoke_##name() at guarded tracepoint call sites drm: Use trace_invoke_##name() at guarded tracepoint call sites HID: Use trace_invoke_##name() at guarded tracepoint call sites i2c: Use trace_invoke_##name() at guarded tracepoint call sites spi: Use trace_invoke_##name() at guarded tracepoint call sites scsi: ufs: Use trace_invoke_##name() at guarded tracepoint call sites btrfs: Use trace_invoke_##name() at guarded tracepoint call sites drivers/accel/habanalabs/common/device.c | 12 ++++++------ drivers/accel/habanalabs/common/mmu/mmu.c | 3 ++- drivers/accel/habanalabs/common/pci/pci.c | 4 ++-- drivers/cpufreq/amd-pstate.c | 10 +++++----- drivers/cpufreq/cpufreq.c | 2 +- drivers/cpufreq/intel_pstate.c | 2 +- drivers/devfreq/devfreq.c | 2 +- drivers/dma-buf/dma-fence.c | 4 ++-- drivers/fsi/fsi-master-aspeed.c | 2 +- drivers/gpu/drm/amd/amdgpu/amdgpu_cs.c | 2 +- drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c | 4 ++-- drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 2 +- drivers/gpu/drm/scheduler/sched_entity.c | 4 ++-- drivers/hid/intel-ish-hid/ipc/pci-ish.c | 2 +- drivers/i2c/i2c-core-slave.c | 2 +- drivers/spi/spi-axi-spi-engine.c | 4 ++-- drivers/ufs/core/ufshcd.c | 12 ++++++------ fs/btrfs/extent_map.c | 4 ++-- fs/btrfs/raid56.c | 4 ++-- include/linux/tracepoint.h | 11 +++++++++++ io_uring/io_uring.h | 2 +- kernel/irq_work.c | 2 +- kernel/sched/ext.c | 2 +- kernel/smp.c | 2 +- net/core/dev.c | 2 +- net/core/xdp.c | 2 +- net/openvswitch/actions.c | 2 +- net/openvswitch/datapath.c | 2 +- net/sctp/outqueue.c | 2 +- net/tipc/node.c | 2 +- 30 files changed, 62 insertions(+), 50 deletions(-) -- 2.53.0

2 months

Professional blockchain investigation services

by schoumachermathieu8＠gmail.com

When someone loses funds to a fake crypto investment platform, recovery can be difficult but not always impossible. Some people contact services like Vault Traces Recovery experts, which specialize in tracking stolen digital assets. The more information you can provide (transaction hashes, platform details, emails, etc.), the better they can analyze the situation. For assistance, Contact them for more info HomePage > Vaulttrades . c o m WhatApp: +1 (570) 291-8211 Mail: info @ vaulttraces . C o m

2 months

Abortion Pills For Sale In Riyadh,(🟡💖🟢)+971568044699(🟡💖🟢 mifepristone and misoprostol available in Riyadh, Cytotec In Riyadh

by kachachaissue12＠gmail.com

Abortion Pills For Sale In Riyadh,(🟡💖🟢)+971568044699(🟡💖🟢 mifepristone and misoprostol available in Riyadh, Cytotec In Riyadh

2 months, 1 week

Abortion Pills For Sale In RAK City, (🟡💖🟢)+971568044699(🟡💖🟢Abortion Pills For Sale In Fujairah, Jebel Ali, Kalba, Abortion Pills For Sale In Khor Fakkan, Umm al-Quwain

by kachachaissue12＠gmail.com

Abortion Pills For Sale In RAK City, (🟡💖🟢)+971568044699(🟡💖🟢Abortion Pills For Sale In Fujairah, Jebel Ali, Kalba, Abortion Pills For Sale In Khor Fakkan, Umm al-Quwain+971568044699 Abortion Pills In Bahrain, +971568044699 Abortion Pills For Sale In Bahrain, +971568044699 Termination Pills Available In Bahrain, +971568044699 Where Can I Buy Cytotec Pills In Bahrain, +971568044699 Misoprostol Pills Available In Bahrain, +971568044699 Misoprostol Tablets Available In Bahrain, +971568044699 +971568044699 Misoprostol Medicine In Bahrain, +971568044699 Mifepristone Pills In Bahrain, +971568044699 Mifepristone Pills In Bahrain, +971568044699 Mifepristone Tablets In Bahrain, +971568044699 Mifepristone Medicine Available In Bahrain, +971568044699 Where Can I Find Mifepristone Pills In Bahrain, +971568044699 Buy Abortion Pills In Bahrain,Cytotec Pills Available In Abu Dhabi, Buy Mifepristone And Misoprostol In Abu Dhabi, Buy cytotec Pills In Abu Dhabi, Buy Abortion pills in Abu Dhabi, Abortion Pills For Sale In Qatar Pharmacy Abortion Pills For Sale In Doha Where to Buy cytotec in Doha Qatar,buy mifepristone and misoprostol in Doha, buy cytotec pills in Doha,Abortion Pills For Sale In Kuwait, buy mifepristone and misoprostol in Kuwait, buy cytotec pills in Kuwait, buy abortion pills in Kuwait, abortion pill in Kuwait, Abortion Pills For Sale In Ras Al Khaimah, buy mifepristone and misoprostol in Ras Al Khaimah, buy cytotec pills in Ras Al Khaimah, buy abortion pills in Ras Al Khaimah … Abortion Pills For Sale In Sharjah, buy mifepristone and misoprostol in Sharjah, buy cytotec pills in Sharjah, buy abortion pills in Sharjah, abortion pill in Sharjah, Abortion Pills For Sale In Dubai Mall, buy mifepristone and misoprostol in Dubai Mall, buy cytotec pills in Dubai Mall, buy abortion pills in Dubai Mall, abortion pill in Dubai … Abortion Pills For Sale In Al Satwa, buy mifepristone and misoprostol in Satwa, buy cytotec pills in Satwa, buy abortion pills in Satwa, abortion pill in Satwa, Abortion Pills For Sale In Ajman, buy mifepristone and misoprostol in Ajman, buy cytotec pills in Ajman, buy abortion pills in Ajman, abortion pill in Ajman, Abortion Pills For Sale In Deira, buy mifepristone and misoprostol in Deira, buy cytotec pills in Deira, buy abortion pills in Deira, abortion pill in Deira, Abortion Pills For Sale In Rak City, buy mifepristone and misoprostol in Rak City, buy cytotec pills in Rak City, buy abortion pills in Rak City, abortion pill in Rak City, Abortion Pills For Sale In Al Ain, buy mifepristone and misoprostol in Al Ain, buy cytotec pills in Al Ain, buy abortion pills in Al Ain, abortion pill in Al Ain,Abortion Pills For Sale In Muscat, buy mifepristone and misoprostol in Muscat, buy cytotec pills in Muscat, buy abortion pills in Muscat, abortion pill in Muscat

2 months, 1 week

Abortion Pills For Sale In Jeddah,(🟡💖🟢)+971568044699(🟡💖🟢 mifepristone and misoprostol available in Jeddah, Buy Cytotec In Jeddah

by kachachaissue12＠gmail.com

Abortion Pills For Sale In Jeddah,(🟡💖🟢)+971568044699(🟡💖🟢 mifepristone and misoprostol available in Jeddah, Buy Cytotec In Jeddah+971568044699 Abortion Pills In Bahrain, +971568044699 Abortion Pills For Sale In Bahrain, +971568044699 Termination Pills Available In Bahrain, +971568044699 Where Can I Buy Cytotec Pills In Bahrain, +971568044699 Misoprostol Pills Available In Bahrain, +971568044699 Misoprostol Tablets Available In Bahrain, +971568044699 +971568044699 Misoprostol Medicine In Bahrain, +971568044699 Mifepristone Pills In Bahrain, +971568044699 Mifepristone Pills In Bahrain, +971568044699 Mifepristone Tablets In Bahrain, +971568044699 Mifepristone Medicine Available In Bahrain, +971568044699 Where Can I Find Mifepristone Pills In Bahrain, +971568044699 Buy Abortion Pills In Bahrain,Cytotec Pills Available In Abu Dhabi, Buy Mifepristone And Misoprostol In Abu Dhabi, Buy cytotec Pills In Abu Dhabi, Buy Abortion pills in Abu Dhabi, Abortion Pills For Sale In Qatar Pharmacy Abortion Pills For Sale In Doha Where to Buy cytotec in Doha Qatar,buy mifepristone and misoprostol in Doha, buy cytotec pills in Doha,Abortion Pills For Sale In Kuwait, buy mifepristone and misoprostol in Kuwait, buy cytotec pills in Kuwait, buy abortion pills in Kuwait, abortion pill in Kuwait, Abortion Pills For Sale In Ras Al Khaimah, buy mifepristone and misoprostol in Ras Al Khaimah, buy cytotec pills in Ras Al Khaimah, buy abortion pills in Ras Al Khaimah … Abortion Pills For Sale In Sharjah, buy mifepristone and misoprostol in Sharjah, buy cytotec pills in Sharjah, buy abortion pills in Sharjah, abortion pill in Sharjah, Abortion Pills For Sale In Dubai Mall, buy mifepristone and misoprostol in Dubai Mall, buy cytotec pills in Dubai Mall, buy abortion pills in Dubai Mall, abortion pill in Dubai … Abortion Pills For Sale In Al Satwa, buy mifepristone and misoprostol in Satwa, buy cytotec pills in Satwa, buy abortion pills in Satwa, abortion pill in Satwa, Abortion Pills For Sale In Ajman, buy mifepristone and misoprostol in Ajman, buy cytotec pills in Ajman, buy abortion pills in Ajman, abortion pill in Ajman, Abortion Pills For Sale In Deira, buy mifepristone and misoprostol in Deira, buy cytotec pills in Deira, buy abortion pills in Deira, abortion pill in Deira, Abortion Pills For Sale In Rak City, buy mifepristone and misoprostol in Rak City, buy cytotec pills in Rak City, buy abortion pills in Rak City, abortion pill in Rak City, Abortion Pills For Sale In Al Ain, buy mifepristone and misoprostol in Al Ain, buy cytotec pills in Al Ain, buy abortion pills in Al Ain, abortion pill in Al Ain,Abortion Pills For Sale In Muscat, buy mifepristone and misoprostol in Muscat, buy cytotec pills in Muscat, buy abortion pills in Muscat, abortion pill in Muscat

2 months, 1 week

Abortion Pills For Sale In Kalba,(🟡💖🟢)+971568044699(🟡💖🟢 Khor Fakkan, Umm al-Quwain

by kachachaissue12＠gmail.com

Abortion Pills For Sale In Kalba,(🟡💖🟢)+971568044699(🟡💖🟢 Khor Fakkan, Umm al-Quwain+971568044699 Abortion Pills In Bahrain, +971568044699 Abortion Pills For Sale In Bahrain, +971568044699 Termination Pills Available In Bahrain, +971568044699 Where Can I Buy Cytotec Pills In Bahrain, +971568044699 Misoprostol Pills Available In Bahrain, +971568044699 Misoprostol Tablets Available In Bahrain, +971568044699 +971568044699 Misoprostol Medicine In Bahrain, +971568044699 Mifepristone Pills In Bahrain, +971568044699 Mifepristone Pills In Bahrain, +971568044699 Mifepristone Tablets In Bahrain, +971568044699 Mifepristone Medicine Available In Bahrain, +971568044699 Where Can I Find Mifepristone Pills In Bahrain, +971568044699 Buy Abortion Pills In Bahrain,Cytotec Pills Available In Abu Dhabi, Buy Mifepristone And Misoprostol In Abu Dhabi, Buy cytotec Pills In Abu Dhabi, Buy Abortion pills in Abu Dhabi, Abortion Pills For Sale In Qatar Pharmacy Abortion Pills For Sale In Doha Where to Buy cytotec in Doha Qatar,buy mifepristone and misoprostol in Doha, buy cytotec pills in Doha,Abortion Pills For Sale In Kuwait, buy mifepristone and misoprostol in Kuwait, buy cytotec pills in Kuwait, buy abortion pills in Kuwait, abortion pill in Kuwait, Abortion Pills For Sale In Ras Al Khaimah, buy mifepristone and misoprostol in Ras Al Khaimah, buy cytotec pills in Ras Al Khaimah, buy abortion pills in Ras Al Khaimah … Abortion Pills For Sale In Sharjah, buy mifepristone and misoprostol in Sharjah, buy cytotec pills in Sharjah, buy abortion pills in Sharjah, abortion pill in Sharjah, Abortion Pills For Sale In Dubai Mall, buy mifepristone and misoprostol in Dubai Mall, buy cytotec pills in Dubai Mall, buy abortion pills in Dubai Mall, abortion pill in Dubai … Abortion Pills For Sale In Al Satwa, buy mifepristone and misoprostol in Satwa, buy cytotec pills in Satwa, buy abortion pills in Satwa, abortion pill in Satwa, Abortion Pills For Sale In Ajman, buy mifepristone and misoprostol in Ajman, buy cytotec pills in Ajman, buy abortion pills in Ajman, abortion pill in Ajman, Abortion Pills For Sale In Deira, buy mifepristone and misoprostol in Deira, buy cytotec pills in Deira, buy abortion pills in Deira, abortion pill in Deira, Abortion Pills For Sale In Rak City, buy mifepristone and misoprostol in Rak City, buy cytotec pills in Rak City, buy abortion pills in Rak City, abortion pill in Rak City, Abortion Pills For Sale In Al Ain, buy mifepristone and misoprostol in Al Ain, buy cytotec pills in Al Ain, buy abortion pills in Al Ain, abortion pill in Al Ain,Abortion Pills For Sale In Muscat, buy mifepristone and misoprostol in Muscat, buy cytotec pills in Muscat, buy abortion pills in Muscat, abortion pill in Muscat

2 months, 1 week

Abortion Pills For Sale In Jebel Ali,(🟡💖🟢)+971568044699(🟡💖🟢 Kalba, Khor Fakkan, Umm al-Quwain

by kachachaissue12＠gmail.com

Abortion Pills For Sale In Jebel Ali,(🟡💖🟢)+971568044699(🟡💖🟢 Kalba, Khor Fakkan, Umm al-Quwain+971568044699 Abortion Pills In Bahrain, +971568044699 Abortion Pills For Sale In Bahrain, +971568044699 Termination Pills Available In Bahrain, +971568044699 Where Can I Buy Cytotec Pills In Bahrain, +971568044699 Misoprostol Pills Available In Bahrain, +971568044699 Misoprostol Tablets Available In Bahrain, +971568044699 +971568044699 Misoprostol Medicine In Bahrain, +971568044699 Mifepristone Pills In Bahrain, +971568044699 Mifepristone Pills In Bahrain, +971568044699 Mifepristone Tablets In Bahrain, +971568044699 Mifepristone Medicine Available In Bahrain, +971568044699 Where Can I Find Mifepristone Pills In Bahrain, +971568044699 Buy Abortion Pills In Bahrain,Cytotec Pills Available In Abu Dhabi, Buy Mifepristone And Misoprostol In Abu Dhabi, Buy cytotec Pills In Abu Dhabi, Buy Abortion pills in Abu Dhabi, Abortion Pills For Sale In Qatar Pharmacy Abortion Pills For Sale In Doha Where to Buy cytotec in Doha Qatar,buy mifepristone and misoprostol in Doha, buy cytotec pills in Doha,Abortion Pills For Sale In Kuwait, buy mifepristone and misoprostol in Kuwait, buy cytotec pills in Kuwait, buy abortion pills in Kuwait, abortion pill in Kuwait, Abortion Pills For Sale In Ras Al Khaimah, buy mifepristone and misoprostol in Ras Al Khaimah, buy cytotec pills in Ras Al Khaimah, buy abortion pills in Ras Al Khaimah … Abortion Pills For Sale In Sharjah, buy mifepristone and misoprostol in Sharjah, buy cytotec pills in Sharjah, buy abortion pills in Sharjah, abortion pill in Sharjah, Abortion Pills For Sale In Dubai Mall, buy mifepristone and misoprostol in Dubai Mall, buy cytotec pills in Dubai Mall, buy abortion pills in Dubai Mall, abortion pill in Dubai … Abortion Pills For Sale In Al Satwa, buy mifepristone and misoprostol in Satwa, buy cytotec pills in Satwa, buy abortion pills in Satwa, abortion pill in Satwa, Abortion Pills For Sale In Ajman, buy mifepristone and misoprostol in Ajman, buy cytotec pills in Ajman, buy abortion pills in Ajman, abortion pill in Ajman, Abortion Pills For Sale In Deira, buy mifepristone and misoprostol in Deira, buy cytotec pills in Deira, buy abortion pills in Deira, abortion pill in Deira, Abortion Pills For Sale In Rak City, buy mifepristone and misoprostol in Rak City, buy cytotec pills in Rak City, buy abortion pills in Rak City, abortion pill in Rak City, Abortion Pills For Sale In Al Ain, buy mifepristone and misoprostol in Al Ain, buy cytotec pills in Al Ain, buy abortion pills in Al Ain, abortion pill in Al Ain,Abortion Pills For Sale In Muscat, buy mifepristone and misoprostol in Muscat, buy cytotec pills in Muscat, buy abortion pills in Muscat, abortion pill in Muscat

2 months, 1 week

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Linaro-mm-sig