- Linux-stable-mirror - lists.linaro.org

FAILED: patch "[PATCH] mm/huge_memory: fix NULL pointer deference when splitting" failed to apply to 6.12-stable tree

by gregkh＠linuxfoundation.org

The patch below does not apply to the 6.12-stable tree. If someone wants it applied there, or to any other stable or longterm tree, then please email the backport, including the original git commit id to <stable(a)vger.kernel.org>. To reproduce the conflict and resubmit, you may use the following commands: git fetch https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/ linux-6.12.y git checkout FETCH_HEAD git cherry-pick -x cff47b9e39a6abf03dde5f4f156f841b0c54bba0 # <resolve conflicts, build, test, etc.> git commit -s git send-email --to '<stable(a)vger.kernel.org>' --in-reply-to '2025120102-geranium-elevator-ca86@gregkh' --subject-prefix 'PATCH 6.12.y' HEAD^.. Possible dependencies: thanks, greg k-h ------------------ original commit in Linus's tree ------------------ From cff47b9e39a6abf03dde5f4f156f841b0c54bba0 Mon Sep 17 00:00:00 2001 From: Wei Yang <richard.weiyang(a)gmail.com> Date: Wed, 19 Nov 2025 23:53:02 +0000 Subject: [PATCH] mm/huge_memory: fix NULL pointer deference when splitting folio Commit c010d47f107f ("mm: thp: split huge page to any lower order pages") introduced an early check on the folio's order via mapping->flags before proceeding with the split work. This check introduced a bug: for shmem folios in the swap cache and truncated folios, the mapping pointer can be NULL. Accessing mapping->flags in this state leads directly to a NULL pointer dereference. This commit fixes the issue by moving the check for mapping != NULL before any attempt to access mapping->flags. Link: https://lkml.kernel.org/r/20251119235302.24773-1-richard.weiyang@gmail.com Fixes: c010d47f107f ("mm: thp: split huge page to any lower order pages") Signed-off-by: Wei Yang <richard.weiyang(a)gmail.com> Reviewed-by: Zi Yan <ziy(a)nvidia.com> Acked-by: David Hildenbrand (Red Hat) <david(a)kernel.org> Reviewed-by: Baolin Wang <baolin.wang(a)linux.alibaba.com> Cc: <stable(a)vger.kernel.org> Signed-off-by: Andrew Morton <akpm(a)linux-foundation.org> diff --git a/mm/huge_memory.c b/mm/huge_memory.c index 2f2a521e5d68..6cba1cb14b23 100644 --- a/mm/huge_memory.c +++ b/mm/huge_memory.c @@ -3619,6 +3619,16 @@ static int __folio_split(struct folio *folio, unsigned int new_order, if (folio != page_folio(split_at) || folio != page_folio(lock_at)) return -EINVAL; + /* + * Folios that just got truncated cannot get split. Signal to the + * caller that there was a race. + * + * TODO: this will also currently refuse shmem folios that are in the + * swapcache. + */ + if (!is_anon && !folio->mapping) + return -EBUSY; + if (new_order >= folio_order(folio)) return -EINVAL; @@ -3659,18 +3669,6 @@ static int __folio_split(struct folio *folio, unsigned int new_order, gfp_t gfp; mapping = folio->mapping; - - /* Truncated ? */ - /* - * TODO: add support for large shmem folio in swap cache. - * When shmem is in swap cache, mapping is NULL and - * folio_test_swapcache() is true. - */ - if (!mapping) { - ret = -EBUSY; - goto out; - } - min_order = mapping_min_folio_order(folio->mapping); if (new_order < min_order) { ret = -EINVAL;

2 weeks, 6 days

3
2
0 0

[PATCH v4 5/7] NTB: epf: vntb: Stop cmd_handler work in epf_ntb_epc_cleanup

by Koichiro Den

Disable the delayed work before clearing BAR mappings and doorbells to avoid running the handler after resources have been torn down. Unable to handle kernel paging request at virtual address ffff800083f46004 [...] Internal error: Oops: 0000000096000007 [#1] SMP [...] Call trace: epf_ntb_cmd_handler+0x54/0x200 [pci_epf_vntb] (P) process_one_work+0x154/0x3b0 worker_thread+0x2c8/0x400 kthread+0x148/0x210 ret_from_fork+0x10/0x20 Cc: <stable(a)vger.kernel.org> Fixes: e35f56bb0330 ("PCI: endpoint: Support NTB transfer between RC and EP") Reviewed-by: Frank Li <Frank.Li(a)nxp.com> Signed-off-by: Koichiro Den <den(a)valinux.co.jp> --- drivers/pci/endpoint/functions/pci-epf-vntb.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/pci/endpoint/functions/pci-epf-vntb.c b/drivers/pci/endpoint/functions/pci-epf-vntb.c index 49ce5d4b0ee5..750a246f79c9 100644 --- a/drivers/pci/endpoint/functions/pci-epf-vntb.c +++ b/drivers/pci/endpoint/functions/pci-epf-vntb.c @@ -823,6 +823,7 @@ static int epf_ntb_epc_init(struct epf_ntb *ntb) */ static void epf_ntb_epc_cleanup(struct epf_ntb *ntb) { + disable_delayed_work_sync(&ntb->cmd_handler); epf_ntb_mw_bar_clear(ntb, ntb->num_mws); epf_ntb_db_bar_clear(ntb); epf_ntb_config_sspad_bar_clear(ntb); -- 2.48.1

2 weeks, 6 days

1
0
0 0

[PATCH v4 4/7] PCI: endpoint: pci-epf-ntb: Remove duplicate resource teardown

by Koichiro Den

epf_ntb_epc_destroy() duplicates the teardown that the caller is supposed to do later. This leads to an oops when .allow_link fails or when .drop_link is performed. Remove the helper. Also drop pci_epc_put(). EPC device refcounting is tied to configfs EPC group lifetime, and pci_epc_put() in the .drop_link path is sufficient. Cc: <stable(a)vger.kernel.org> Fixes: 8b821cf76150 ("PCI: endpoint: Add EP function driver to provide NTB functionality") Reviewed-by: Frank Li <Frank.Li(a)nxp.com> Signed-off-by: Koichiro Den <den(a)valinux.co.jp> --- drivers/pci/endpoint/functions/pci-epf-ntb.c | 56 +------------------- 1 file changed, 2 insertions(+), 54 deletions(-) diff --git a/drivers/pci/endpoint/functions/pci-epf-ntb.c b/drivers/pci/endpoint/functions/pci-epf-ntb.c index e01a98e74d21..7702ebb81d99 100644 --- a/drivers/pci/endpoint/functions/pci-epf-ntb.c +++ b/drivers/pci/endpoint/functions/pci-epf-ntb.c @@ -1494,47 +1494,6 @@ static int epf_ntb_db_mw_bar_init(struct epf_ntb *ntb, return ret; } -/** - * epf_ntb_epc_destroy_interface() - Cleanup NTB EPC interface - * @ntb: NTB device that facilitates communication between HOST1 and HOST2 - * @type: PRIMARY interface or SECONDARY interface - * - * Unbind NTB function device from EPC and relinquish reference to pci_epc - * for each of the interface. - */ -static void epf_ntb_epc_destroy_interface(struct epf_ntb *ntb, - enum pci_epc_interface_type type) -{ - struct epf_ntb_epc *ntb_epc; - struct pci_epc *epc; - struct pci_epf *epf; - - if (type < 0) - return; - - epf = ntb->epf; - ntb_epc = ntb->epc[type]; - if (!ntb_epc) - return; - epc = ntb_epc->epc; - pci_epc_remove_epf(epc, epf, type); - pci_epc_put(epc); -} - -/** - * epf_ntb_epc_destroy() - Cleanup NTB EPC interface - * @ntb: NTB device that facilitates communication between HOST1 and HOST2 - * - * Wrapper for epf_ntb_epc_destroy_interface() to cleanup all the NTB interfaces - */ -static void epf_ntb_epc_destroy(struct epf_ntb *ntb) -{ - enum pci_epc_interface_type type; - - for (type = PRIMARY_INTERFACE; type <= SECONDARY_INTERFACE; type++) - epf_ntb_epc_destroy_interface(ntb, type); -} - /** * epf_ntb_epc_create_interface() - Create and initialize NTB EPC interface * @ntb: NTB device that facilitates communication between HOST1 and HOST2 @@ -1614,15 +1573,8 @@ static int epf_ntb_epc_create(struct epf_ntb *ntb) ret = epf_ntb_epc_create_interface(ntb, epf->sec_epc, SECONDARY_INTERFACE); - if (ret) { + if (ret) dev_err(dev, "SECONDARY intf: Fail to create NTB EPC\n"); - goto err_epc_create; - } - - return 0; - -err_epc_create: - epf_ntb_epc_destroy_interface(ntb, PRIMARY_INTERFACE); return ret; } @@ -1887,7 +1839,7 @@ static int epf_ntb_bind(struct pci_epf *epf) ret = epf_ntb_init_epc_bar(ntb); if (ret) { dev_err(dev, "Failed to create NTB EPC\n"); - goto err_bar_init; + return ret; } ret = epf_ntb_config_spad_bar_alloc_interface(ntb); @@ -1909,9 +1861,6 @@ static int epf_ntb_bind(struct pci_epf *epf) err_bar_alloc: epf_ntb_config_spad_bar_free(ntb); -err_bar_init: - epf_ntb_epc_destroy(ntb); - return ret; } @@ -1927,7 +1876,6 @@ static void epf_ntb_unbind(struct pci_epf *epf) epf_ntb_epc_cleanup(ntb); epf_ntb_config_spad_bar_free(ntb); - epf_ntb_epc_destroy(ntb); } #define EPF_NTB_R(_name) \ -- 2.48.1

2 weeks, 6 days

1
0
0 0

[PATCH v4 3/7] PCI: endpoint: pci-epf-vntb: Remove duplicate resource teardown

by Koichiro Den

epf_ntb_epc_destroy() duplicates the teardown that the caller is supposed to perform later. This leads to an oops when .allow_link fails or when .drop_link is performed. The following is an example oops of the former case: Unable to handle kernel paging request at virtual address dead000000000108 [...] [dead000000000108] address between user and kernel address ranges Internal error: Oops: 0000000096000044 [#1] SMP [...] Call trace: pci_epc_remove_epf+0x78/0xe0 (P) pci_primary_epc_epf_link+0x88/0xa8 configfs_symlink+0x1f4/0x5a0 vfs_symlink+0x134/0x1d8 do_symlinkat+0x88/0x138 __arm64_sys_symlinkat+0x74/0xe0 [...] Remove the helper, and drop pci_epc_put(). EPC device refcounting is tied to the configfs EPC group lifetime, and pci_epc_put() in the .drop_link path is sufficient. Cc: <stable(a)vger.kernel.org> Fixes: e35f56bb0330 ("PCI: endpoint: Support NTB transfer between RC and EP") Reviewed-by: Frank Li <Frank.Li(a)nxp.com> Signed-off-by: Koichiro Den <den(a)valinux.co.jp> --- drivers/pci/endpoint/functions/pci-epf-vntb.c | 19 +------------------ 1 file changed, 1 insertion(+), 18 deletions(-) diff --git a/drivers/pci/endpoint/functions/pci-epf-vntb.c b/drivers/pci/endpoint/functions/pci-epf-vntb.c index 83e9ab10f9c4..49ce5d4b0ee5 100644 --- a/drivers/pci/endpoint/functions/pci-epf-vntb.c +++ b/drivers/pci/endpoint/functions/pci-epf-vntb.c @@ -644,19 +644,6 @@ static void epf_ntb_mw_bar_clear(struct epf_ntb *ntb, int num_mws) } } -/** - * epf_ntb_epc_destroy() - Cleanup NTB EPC interface - * @ntb: NTB device that facilitates communication between HOST and VHOST - * - * Wrapper for epf_ntb_epc_destroy_interface() to cleanup all the NTB interfaces - */ -static void epf_ntb_epc_destroy(struct epf_ntb *ntb) -{ - pci_epc_remove_epf(ntb->epf->epc, ntb->epf, 0); - pci_epc_put(ntb->epf->epc); -} - - /** * epf_ntb_is_bar_used() - Check if a bar is used in the ntb configuration * @ntb: NTB device that facilitates communication between HOST and VHOST @@ -1406,7 +1393,7 @@ static int epf_ntb_bind(struct pci_epf *epf) ret = epf_ntb_init_epc_bar(ntb); if (ret) { dev_err(dev, "Failed to create NTB EPC\n"); - goto err_bar_init; + return ret; } ret = epf_ntb_config_spad_bar_alloc(ntb); @@ -1446,9 +1433,6 @@ static int epf_ntb_bind(struct pci_epf *epf) err_bar_alloc: epf_ntb_config_spad_bar_free(ntb); -err_bar_init: - epf_ntb_epc_destroy(ntb); - return ret; } @@ -1464,7 +1448,6 @@ static void epf_ntb_unbind(struct pci_epf *epf) epf_ntb_epc_cleanup(ntb); epf_ntb_config_spad_bar_free(ntb); - epf_ntb_epc_destroy(ntb); pci_unregister_driver(&vntb_pci_driver); } -- 2.48.1

2 weeks, 6 days

1
0
0 0

[PATCH v4 2/7] PCI: endpoint: Fix parameter order for .drop_link

by Koichiro Den

The unlink callbacks passed the parameters in the wrong order that led to looking up the wrong group objects. Swap the arguments so that the first parameter is the epf item and the second is the epc item. Cc: <stable(a)vger.kernel.org> Fixes: e85a2d783762 ("PCI: endpoint: Add support in configfs to associate two EPCs with EPF") Reviewed-by: Frank Li <Frank.Li(a)nxp.com> Signed-off-by: Koichiro Den <den(a)valinux.co.jp> --- drivers/pci/endpoint/pci-ep-cfs.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/drivers/pci/endpoint/pci-ep-cfs.c b/drivers/pci/endpoint/pci-ep-cfs.c index ef50c82e647f..c7cf6c76d116 100644 --- a/drivers/pci/endpoint/pci-ep-cfs.c +++ b/drivers/pci/endpoint/pci-ep-cfs.c @@ -69,8 +69,8 @@ static int pci_secondary_epc_epf_link(struct config_item *epf_item, return 0; } -static void pci_secondary_epc_epf_unlink(struct config_item *epc_item, - struct config_item *epf_item) +static void pci_secondary_epc_epf_unlink(struct config_item *epf_item, + struct config_item *epc_item) { struct pci_epf_group *epf_group = to_pci_epf_group(epf_item->ci_parent); struct pci_epc_group *epc_group = to_pci_epc_group(epc_item); @@ -133,8 +133,8 @@ static int pci_primary_epc_epf_link(struct config_item *epf_item, return 0; } -static void pci_primary_epc_epf_unlink(struct config_item *epc_item, - struct config_item *epf_item) +static void pci_primary_epc_epf_unlink(struct config_item *epf_item, + struct config_item *epc_item) { struct pci_epf_group *epf_group = to_pci_epf_group(epf_item->ci_parent); struct pci_epc_group *epc_group = to_pci_epc_group(epc_item); -- 2.48.1

2 weeks, 6 days

1
0
0 0

[PATCH v4 1/7] NTB: epf: Avoid pci_iounmap() with offset when PEER_SPAD and CONFIG share BAR

by Koichiro Den

When BAR_PEER_SPAD and BAR_CONFIG share one PCI BAR, the module teardown path ends up calling pci_iounmap() on the same iomem with some offset, which is unnecessary and triggers a kernel warning like the following: Trying to vunmap() nonexistent vm area (0000000069a5ffe8) WARNING: mm/vmalloc.c:3470 at vunmap+0x58/0x68, CPU#5: modprobe/2937 [...] Call trace: vunmap+0x58/0x68 (P) iounmap+0x34/0x48 pci_iounmap+0x2c/0x40 ntb_epf_pci_remove+0x44/0x80 [ntb_hw_epf] pci_device_remove+0x48/0xf8 device_remove+0x50/0x88 device_release_driver_internal+0x1c8/0x228 driver_detach+0x50/0xb0 bus_remove_driver+0x74/0x100 driver_unregister+0x34/0x68 pci_unregister_driver+0x34/0xa0 ntb_epf_pci_driver_exit+0x14/0xfe0 [ntb_hw_epf] [...] Fix it by unmapping only when PEER_SPAD and CONFIG use difference bars. Cc: <stable(a)vger.kernel.org> Fixes: e75d5ae8ab88 ("NTB: epf: Allow more flexibility in the memory BAR map method") Reviewed-by: Frank Li <Frank.Li(a)nxp.com> Signed-off-by: Koichiro Den <den(a)valinux.co.jp> --- drivers/ntb/hw/epf/ntb_hw_epf.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/drivers/ntb/hw/epf/ntb_hw_epf.c b/drivers/ntb/hw/epf/ntb_hw_epf.c index d3ecf25a5162..9935da48a52e 100644 --- a/drivers/ntb/hw/epf/ntb_hw_epf.c +++ b/drivers/ntb/hw/epf/ntb_hw_epf.c @@ -646,7 +646,8 @@ static void ntb_epf_deinit_pci(struct ntb_epf_dev *ndev) struct pci_dev *pdev = ndev->ntb.pdev; pci_iounmap(pdev, ndev->ctrl_reg); - pci_iounmap(pdev, ndev->peer_spad_reg); + if (ndev->barno_map[BAR_PEER_SPAD] != ndev->barno_map[BAR_CONFIG]) + pci_iounmap(pdev, ndev->peer_spad_reg); pci_iounmap(pdev, ndev->db_reg); pci_release_regions(pdev); -- 2.48.1

2 weeks, 6 days

1
0
0 0

[PATCH v3 0/7] PCI: endpoint/NTB: Harden vNTB resource management

by Koichiro Den

The vNTB endpoint function (pci-epf-vntb) can be configured and reconfigured through configfs (link/unlink functions, start/stop the controller, update parameters). In practice, several pitfalls present: double-unmapping when two windows share a BAR, wrong parameter order in .drop_link leading to wrong object lookups, duplicate EPC teardown that leads to oopses, a work item running after resources were torn down, and inability to re-link/restart fundamentally because ntb_dev was embedded and the vPCI bus teardown was incomplete. This series addresses those issues and hardens resource management across NTB EPF and PCI EP core: - Avoid double iounmap when PEER_SPAD and CONFIG share the same BAR. - Fix configfs .drop_link parameter order so the correct groups are used during unlink. - Remove duplicate EPC resource teardown in both pci-epf-vntb and pci-epf-ntb, avoiding crashes on .allow_link failures and during .drop_link. - Stop the delayed cmd_handler work before clearing BARs/doorbells. - Manage ntb_dev as a devm-managed allocation and implement .remove() in the vNTB PCI driver. Switch to pci_scan_root_bus(). With these changes, the controller can now be stopped, a function unlinked, configfs settings updated, and the controller re-linked and restarted without rebooting the endpoint, as long as the underlying pci_epc_ops .stop() is non-destructive and .start() restores normal operation. Patches 1-5 carry Fixes tags and are candidates for stable. Patch 6 is a preparatory one for Patch 7. Patch 7 is a behavioral improvement that completes lifetime management for relink/restart scenarios. Apologies for the delay between v2 and v3, and thank you for the review. v2->v3 changes: - Added Reviewed-by tag for [PATCH v2 4/6] - Split [PATCH v2 6/6] into two, based on the feedback from Frank. (No code changes overall.) v1->v2 changes: - Incorporated feedback from Frank. - Added Reviewed-by tags (except for patches #4 and #6). - Fixed a typo in patch #5 title. (No code changes overall.) v2: https://lore.kernel.org/all/20251029080321.807943-1-den@valinux.co.jp/ v1: https://lore.kernel.org/all/20251023071757.901181-1-den@valinux.co.jp/ Koichiro Den (7): NTB: epf: Avoid pci_iounmap() with offset when PEER_SPAD and CONFIG share BAR PCI: endpoint: Fix parameter order for .drop_link PCI: endpoint: pci-epf-vntb: Remove duplicate resource teardown PCI: endpoint: pci-epf-ntb: Remove duplicate resource teardown NTB: epf: vntb: Stop cmd_handler work in epf_ntb_epc_cleanup PCI: endpoint: pci-epf-vntb: Switch vpci_scan_bus() to use pci_scan_root_bus() PCI: endpoint: pci-epf-vntb: Manage ntb_dev lifetime and fix vpci bus teardown drivers/ntb/hw/epf/ntb_hw_epf.c | 3 +- drivers/pci/endpoint/functions/pci-epf-ntb.c | 56 +----------- drivers/pci/endpoint/functions/pci-epf-vntb.c | 86 ++++++++++++------- drivers/pci/endpoint/pci-ep-cfs.c | 8 +- 4 files changed, 62 insertions(+), 91 deletions(-) -- 2.48.1

2 weeks, 6 days

3
11
0 0

How To Correct Name on JetBlue Flight Ticket?

by taige52＠netaxistech.com

Correcting a name on a JetBlue flight ticket doesn’t have to be a daunting task. This guide is designed to help travelers easily understand the steps and fees involved in making name corrections. Whether it’s a minor typo or a major change due to a life event, ensuring your name matches your government ID is crucial for a hassle-free journey. Read this blog on to learn how to handle name corrections efficiently and ensure your travel plans proceed without any issues. What is the policy of changing name on JetBlue? Before you proceed to change your name, you must be well versed with its name changing policy which will help you, JetBlue Name Change Policy includes the following criteria: Validation by JetBlue: The ticket must be validated by JetBlue (B6/279), and all flights on the ticket must be either operated or validated by JetBlue. Single Reissue: Only one reissue per ticket is allowed for a name correction. Any additional name corrections are treated as name changes and will incur change fees and fare increases. Flight and Fare Restrictions: Changes to flights, travel dates, fare classes, or fare basis codes are not permitted. If the original fare is unavailable, refer to specific instructions. Mid-Travel Corrections: Minor name corrections are allowed mid-travel to match the government-issued ID or passport, ensuring the passenger's identity is consistent throughout the journey. Date of Birth and Gender: The date of birth and gender cannot be changed in conjunction with a name correction. Altering both the date of birth and the name is considered a name change and falls under the Name Change Policy. Booking Errors: Minor corrections to the date of birth are permitted due to booking errors, provided the name remains unchanged. Single Correction Rule: Only one correction per customer is allowed. Any further changes will adhere to the Name Change Policy. How much will it cost to make JetBlue name changes? Changing a name on a JetBlue ticket comes with specific costs that vary depending on several factors. For Blue Basic seat holders, the fee is typically $100 for domestic flights, but this charge can rise to $200 for international flights beyond the USA, Mexico, or Central America. For passengers traveling with Blue, Blue Extra, Blue Refundable, Blue Plus, Blue Plus Refundable, Mint, and Mint Refundable tickets, name corrections can be made by covering the fare difference. If you choose to correct the name offline, be prepared to pay a bit more, with fees starting at $50, depending on the fare type. Special situations, such as name changes due to marriage, adoption, or divorce, may also incur varying costs based on the specifics of the case as per the JetBlue Airways name change policy. It's important to note that only one name change per passenger is allowed. If you need to modify the name more than once, you will have to pay the designated fee for each subsequent change. What is the process of modifying name on JetBlue tickets? Make sure JetBlue (B6/279) is the carrier for your flight. Have your government ID or passport ready. For name changes due to marriage, divorce, or adoption, have those legal documents too. Reach out to JetBlue customer service online, by phone, or at the airport. Tell them about the name correction you need. Explain if it’s a small fix (like a typo) or a big change. Ensure your date of birth and gender stay the same. Pay the required fee. Blue Basic seats might cost $100 for domestic or up to $200 for international flights. Other fare types might just need a fare difference payment. Once the correction is done and fees are paid, check your updated ticket to make sure everything is correct. Only one name change per ticket is allowed. Any further changes will cost extra. By following these steps, you can easily correct your name on JetBlue tickets and keep your travel plans on track. You can call JetBlue at +1 (866) 897-5122 for doing it over a call or need help. What is the acceptable name change on JetBlue? JetBlue’s Name Correction Policy offers flexibility for passengers needing to adjust their names on tickets to align with their government-issued ID or passport. This policy covers a range of changes, ensuring that travelers can rectify mistakes or update their names due to significant life events without undue hassle. Acceptable modifications include correcting misspellings in first, middle, or last names, switching from a nickname to a legal name, and resolving inverted names. Additionally, passengers can add a middle name or an extra last name if required. The policy also caters to more substantial changes, such as those resulting from marriage, divorce, or adoption. These updates are crucial for reflecting the new legal name accurately. Importantly, JetBlue requires that the date of birth and gender remain unchanged to maintain the consistency of the passenger's identity. In cases where an error isn't corrected before the first leg of travel, JetBlue permits mid-travel name corrections under the same guidelines. This provision ensures that even in the midst of a journey, passengers can amend their name details to avoid any issues during their travels. JetBlue offers a simply easy process for name corrections, tailored to accommodate both minor errors and significant changes resulting from life events like marriage, divorce, or adoption. You can call +1 (866) 897-5122 to know more.

2 weeks, 6 days

1
0
0 0

How To Talk To a Live Person at Lufthansa Airlines?

by taige52＠netaxistech.com

Trying to get in touch with a live person at Lufthansa Airlines can feel like a quest for hidden treasure. Whether it's resolving a booking issue, making a last-minute change, or simply seeking information, speaking directly to a human can make all the difference. This guide provides you with the essential steps to connect with a real representative at Lufthansa, ensuring your questions are answered swiftly and effectively. Discover how easy it can be to get the help you need with just a few clicks or a quick call through this blog . How to contact the Lufthansa Airlines customer service? Reaching out to Lufthansa Airlines for assistance is a breeze. Here’s how you can do it: Open your web browser and head over to Lufthansa’s official website. It’s your starting point for all things related to their services. Scroll to the bottom of the homepage. There, you’ll spot a link labeled "Help & Contact." Click on it to access the customer service options. You’ll find various ways to get in touch. Whether you prefer calling, emailing, or chatting online, they’ve got you covered. Pick the option that suits you best. If you prefer talking to someone directly, call Lufthansa customer service hotline at +1-800-645-3880 or +1 (866) 897-5122. Keep your booking details handy for a smoother conversation. If your issue isn’t urgent, consider sending an email. Look for the customer service email address in the contact section and draft a detailed message explaining your concern. Lufthansa is also active on social media platforms like Twitter and Facebook. You can send them a message or tweet at them for assistance. If you prefer face-to-face interaction, find the nearest Lufthansa office. Addresses and office hours are listed on their website. If you have the Lufthansa app installed, you can access customer service directly through it. The app provides a convenient way to manage your booking and get support on the go. With these steps, getting the help you need from Lufthansa customer service is simple and easy. What advantages can I get by contacting the Lufthansa Airlines customer service? Contacting Lufthansa Airlines customer service can significantly enhance your travel experience in numerous ways. First and foremost, their knowledgeable representatives can assist you with any booking modifications you might need. Whether it's changing flight dates, upgrading your seat, or adding extra baggage, they ensure your trip is tailored to your preferences without any hassle. Another major advantage is their ability to provide up-to-date information about your flight status. If there's a delay or change in your flight schedule, customer service can keep you informed, helping you avoid unnecessary stress and allowing you to plan accordingly. They can also assist you with any special requests, such as meal preferences, wheelchair assistance, or seating arrangements, ensuring your comfort throughout the journey. Lufthansa customer service also excels in resolving issues efficiently. If you encounter problems like lost luggage or ticketing errors, their team is equipped to handle such situations promptly, providing peace of mind. Additionally, their multilingual support ensures that language barriers are not an obstacle, making communication easy and effective for travelers from around the world. By reaching out to Lufthansa Airlines customer service, you gain a reliable partner in your travel journey, dedicated to making every aspect of your trip smoother and more enjoyable. Can I have a live chat with Lufthansa? Yes, you can have a live chat with Lufthansa, and it’s a straightforward process. When you need immediate assistance or have questions that require quick responses, the live chat feature on Lufthansa’s website is your go-to option. To get started, head over to the Lufthansa website and look for the "Help & Contact" page. Once there, you will see an icon resembling a message box. Clicking on this icon will connect you with a live representative who is ready to assist you. This feature is particularly useful for resolving issues on the spot, whether it’s inquiries about your booking, flight changes, or any special requests you might have. The Lufthansa live chat option provides a direct line to a knowledgeable representative, ensuring your concerns are addressed promptly. It’s a convenient way to get the help you need without having to wait on hold or navigate through automated phone menus. Whether you’re at home or on the go, Lufthansa’s live chat service offers a reliable and efficient way to get support, making your travel experience smoother and more enjoyable. Reaching a live person at Lufthansa Airlines doesn't have to be a daunting task. By following the steps outlined in this guide, you can connect with a knowledgeable representative who can assist with any queries or issues you might have. Whether you choose to use the live chat feature on their website, dial +1 (866) 897-5122 for direct support, or explore other contact options, knowing how to get in touch effectively can significantly enhance your travel experience. Remember, Lufthansa customer service team is there to help make your journey smoother and more enjoyable, providing the assistance you need when you need it most.

2 weeks, 6 days

1
0
0 0

How can you Get a Hold of Turkish Airlines?

by taige52＠netaxistech.com

Be if you're planning your next adventure or need assistance with existing reservations, reaching out is simple and efficient. Explore multiple communication channels designed to cater to your needs, ensuring personalized support and timely solutions. From phone consultations to online chats and email correspondence, Turkish Airlines provides accessible avenues as elaborated. How to get a hold of Turkish Airlines? These are the steps to contact Turkish Airlines Customer Service: Begin by grabbing your phone and punch in 800-874-8875. If you are wanting less queue on call, use +1 (866) 897-5122. These numbers are at your service around the clock. Pay attention to the automated menu options to choose the right department. Press the number that matches your issue, like reservations or baggage. Keep your flight details and booking reference handy to speed up the process. Explain your problem or question clearly to the customer service agent. Listen to the solutions or instructions they provide. Write down any important information, like reference numbers or agent names. You can ask them for any other help related to your flights, they will be happy to assist you. By following these steps, you can effectively reach out to Turkish Airlines and get the assistance you need, ensuring your travel experience is as smooth as possible. But don’t forget there are many other ways as well for you to be connected with Turkish Airlines, check the next section for the same. What are some other ways than calling Turkish Airlines? Aside from calling Turkish Airlines directly at +1 (866) 897-5122, there are several other convenient ways to get in touch with them. One effective method is through their online chat service, where you can connect with a live agent by clicking the message box and typing "Chat with Agent." This virtual assistance directs you to real-time chat conversations, allowing you to discuss your queries or concerns without waiting on hold. Another option is to send an email to NYC.TICKETING(a)THY.COM. This method provides a written record of your communication and allows you to detail your issue or request in a clear, organized manner. Expect a response within a reasonable timeframe as their team addresses your inquiries promptly. For those preferring traditional correspondence, you can mail Turkish Airlines at their General Management Building located at Ataturk Airport, Yesilkoy 34149 Istanbul, Türkiye. Sending a letter ensures your message is received directly by their headquarters, maintaining a personal touch in your communication. Lastly, if you prefer a more formal approach, you can fax them at 001-718-751-2688. This method is suitable for sending documents or detailed information that may require a physical copy for reference. What benefit do you get by contacting Turkish Airlines customer service? Contacting Turkish Airlines customer assistance offers significant benefits beyond resolving immediate issues. It provides a direct channel for passengers to voice their feedback, concerns, and suggestions, knowing that every comment is valued regardless of its economic impact. This engagement is reinforced by a robust compensation scheme aimed at ensuring customer satisfaction, reflecting a commitment to accountability and transparency in service delivery. Passengers can expect a personalized approach to resolving complaints, guided by principles of fairness and objectivity. The process involves careful analysis and proactive steps to find suitable solutions, fostering a sense of trust and reliability in Turkish Airlines' commitment to customer welfare. Moreover, the information gathered from these interactions contributes to continuous improvement efforts, driving enhancements in products and services based on real customer experiences and needs. Contacting Turkish customer service at +1 (866) 897-5122 allows passengers to stay informed about their rights and entitlements under national and international regulations, ensuring they receive fair treatment and support. This proactive engagement not only resolves immediate concerns but also strengthens the airline's relationship with its customers, promoting a positive experience that extends beyond the flight itself. Ultimately, it empowers passengers to actively participate in shaping the quality and standards of service they receive from Turkish Airlines. Can I book a flight without paying Turkish Airlines? Yes, Turkish Airlines offers a "Hold the Price" option that allows you to book a flight without immediately paying. This feature is ideal if you've found the right flight but need more time to finalize your plans or secure funds. By selecting "Hold the Price," you can lock in the ticket price for a specified period by paying a hold fee upfront. This fee is later refunded if you complete the ticket purchase within the hold period. Here's how it works: During the booking process, after selecting your flight and entering passenger details, you can choose the "Hold the Price" option. This ensures that the flight's price remains unchanged for the duration of the hold period, offering peace of mind while you confirm your travel arrangements. Once you've completed this step and paid the hold fee, the ticket is temporarily reserved under your name. To finalize your booking, you'll need to log into your Turkish Airlines account and navigate to the "My Reservations" section. From there, simply proceed to complete the purchase by clicking the "Pay and fly" button before the hold period expires. This option provides flexibility and assurance, allowing you to secure your preferred flight without immediate payment, ensuring you don't miss out on a favorable fare. With dedicated channels for feedback, complaints, and inquiries, passengers can rest assured that their voices are heard and valued at +1 (866) 897-5122. Whether securing a hold on ticket prices or finalizing bookings hassle-free, Turkish Airlines & prioritizes customer satisfaction at every step.

2 weeks, 6 days

1
0
0 0

How Can I Speak to Someone at Southwest Airlines?

by taige52＠netaxistech.com

Finding a real person to talk to at Southwest Airlines doesn't have to feel like finding a needle in a haystack. We empathize with the frustration of automated systems and endless phone menus. This page is your guide to speaking with a live representative at Southwest Airlines with ease. Whether you have questions about your upcoming flight, need assistance with booking or changing your reservation, or simply want to chat with someone directly, here to help you navigate the process smoothly. Say goodbye to automated prompts and hello to personalized assistance from a Southwest representative. What is the process of talking to someone at Southwest? When you call someone at Southwest for getting assistance regarding your flight tickets, you know it is the fastest way to connect with them. Here's a step-by-step guide to talking to someone at Southwest Airlines: Dial the Southwest customer service numbers: +1-800-435-9792 or +1 (866) 897-5122 (for least wait time). Listen carefully to the automated menu options. Select the appropriate option for speaking with a live representative. Be patient if there's a wait time to connect to an agent. Once connected, introduce yourself politely and state your inquiry. Provide any necessary information, such as your flight details or booking number. Listen attentively to the representative's instructions or questions. Follow any instructions provided and respond accordingly. Thank the representative for their assistance before ending the call. Make note of any important information provided during the call for reference. Through following such simple steps, you will gather the assistance required from the Southwest travel experts over a conversation on call. Moreover, you should know that you have many other ways of reaching out to the customer support of Southwest which is elaborated on the next section of this blog. Can I connect with Southwest without calling? Yes, you can connect with Southwest Airlines without having to make a phone call. They offer alternative communication methods to cater to different preferences and situations. One option is through email. By visiting their help center, passengers can select the "Email Us" option and choose the genre of their email, whether it's a complaint, question, or compliment for the airline. This allows for written communication, providing a convenient way to address inquiries or concerns without the need for a phone call. Additionally, Southwest Airlines offers a chat feature on their help center page. By selecting the chat option, passengers can engage in real-time conversation with a chat representative. This provides an interactive platform for seeking assistance with flight-related queries, booking issues, or other travel-related matters. Chat support offers the advantage of immediate responses and can be especially helpful for resolving issues quickly or obtaining information promptly. These alternative methods of communication enhance accessibility and convenience for passengers, ensuring that they can reach out to Southwest Airlines in a way that best suits their preferences and circumstances. Whether through email or chat, Southwest is committed to providing responsive and helpful customer service to ensure a positive travel experience for all passengers. How can I connect with Southwest from other countries? For travelers reaching out to Southwest Airlines from various countries, there are dedicated contact numbers available to ensure easy communication and assistance. From Aruba, passengers can dial 588-2900, while those in the Bahamas can reach Southwest by calling 1-866-897-5122. Additionally, Spanish-speaking passengers in the Bahamas can use the number 1-866-897-5122 for assistance. In Belize, passengers can connect with Southwest by dialing 0-800-0078684, or 0-800-247-5463 for Spanish-language support. For travelers in Costa Rica, Southwest can be reached at 0-800-012-1916, or 0-800-012-1917 for Spanish-speaking assistance. Passengers in the Dominican Republic can reach Southwest by dialing 1-800-751-9039, or 1-866-897-5122 for Spanish-language support. From Grand Cayman, passengers can connect with Southwest at 1-866-897-5122 for Spanish-speaking assistance. Travelers in Jamaica can reach Southwest by dialing 1-866-4897-5122, for Spanish-language support. In Mexico, passengers can contact Southwest at 866-897-5122 for Spanish-speaking assistance. These dedicated contact numbers ensure that passengers from various countries can easily reach Southwest Airlines for assistance with their travel needs. Whether it's booking inquiries, flight changes, or general assistance, Southwest Airlines aims to provide accessible customer service to all passengers, regardless of their location. In conclusion, connecting with a live person at Southwest Airlines is now simpler than ever with our guidance. Whether you need help with your booking, have questions about your flight, or require assistance with any other travel-related matters, ensures you can connect with a real person at Southwest Airlines at +1-800-435-9792 or +1 (866) 897-5122 quickly and efficiently. Say goodbye to frustrating phone menus and hello to personalized customer service that puts your needs first. So, next time you need assistance with Southwest Airlines, just dial the provided number and let help you speak to a live person effortlessly.

2 weeks, 6 days

1
0
0 0

How Can I Talk To Someone At Copa Airlines?

by taige52＠netaxistech.com

Finding answers or assistance with Copa Airlines shouldn't feel like navigating a maze. They understand the frustrations of needing to speak with a real person when it comes to your travel concerns. Whether it's a burning question about your flight, a sudden change in plans, or simply seeking reassurance, reaching out to someone at Copa Airlines should be straightforward and stress-free. Let guide you through the process, ensuring that you connect with a knowledgeable representative who's ready to address your needs and provide the assistance you're looking for. What is the process of connecting with the Copa customer service? Here's a step-by-step guide on how to connect with Copa Airlines customer service: Whether it's your smartphone, tablet, or computer, get ready to reach out to Copa Airlines. If you prefer calling, you can dial the number you provided, +1 786 840-2672 or +1 (866) 897-5122 Remember to double-check the number to ensure accuracy. Sometimes, there might be a bit of a wait before you're connected to a representative. It's all part of the process, so hang in there! Once connected, you'll likely be greeted by a friendly voice on the other end. Don't hesitate to return the warmth! Be it if it's a question about your booking, a concern about your flight, or anything else related to Copa Airlines, explain your query clearly and concisely. For security purposes, the representative might ask you to verify some details, such as your booking number or personal information. Pay close attention to what the representative says and follow any instructions they provide. Clear communication is key! The representative will do their best to assist you with your query or concern. If it's something they can't resolve immediately, they'll guide you on the next steps. Once your query has been addressed or your concern resolved, don't forget to thank the representative for their help. A little gratitude goes a long way! If necessary, jot down any important information provided during the call, such as reference numbers or next steps. Remember, connecting with customer service can sometimes be a bit daunting, but the Copa Airlines team is there to help you every step of the way. So, take a deep breath, dial the number, and let them assist you with whatever you need! What are some other ways of contacting Copa Airlines? Aside from calling and submitting forms online, there are a couple of other ways you can get in touch with Copa Airlines. One option is via email. You can find their email address on their official website under the "Contact Us" section. Sending an email allows you to lay out your concerns in detail and provides a written record of your communication. Another way to contact Copa Airlines is through their live chat feature, if available. This feature allows you to chat with a customer service representative in real-time, similar to instant messaging. It's a convenient option if you prefer typing your questions or if you need assistance while browsing their website. Additionally, if you happen to be near one of their physical locations, you can always visit a Copa Airlines ticket office or service center in person. Speaking face-to-face with a representative can sometimes provide a more personalized and immediate solution to your inquiries or issues. Remember, whichever method you choose to contact Copa Airlines, their dedicated team is there to assist you and ensure your travel experience is as smooth as possible. Whether it's via email, live chat, or in person, don't hesitate to reach out if you have any questions or concerns. What if I want to call Copa from Mexico? If you're reaching out to Copa Airlines from Mexico, you can connect with them using a specific phone number dedicated to assisting passengers in Mexico. Just dial (5255) 1516 3319 or +1 (866) 897-5122 to get in touch with Copa's customer service team. This number is tailored to cater to passengers located in Mexico, ensuring a direct and efficient line of communication. Whether you have questions about your flight, need assistance with booking or managing your reservation, or require support with any other travel-related matters, Copa's representatives are ready to assist you. Be sure to have your booking details or any relevant information on hand when you call to help expedite the process. No matter where you are in Mexico, whether planning your trip or already on your journey, Copa Airlines is committed to providing reliable and responsive customer service to ensure a smooth travel experience for all passengers. So, don't hesitate to give them a call whenever you need assistance or have inquiries regarding your Copa Airlines travel plans. What kind of help does Copa Airlines customer service offers? Help with reservations, changes, and special requests. Queries about schedules, delays, or cancellations. Guidance on allowances, restrictions, and lost luggage procedures. Assistance with choosing, changing, or upgrading seats. Support for passengers with disabilities, medical needs, or infants. Information about Copa's frequent flyer program and benefits. Help with payments, refunds, or billing inquiries. Assistance regarding visas, passports, and required paperwork. Queries about meals, entertainment, or amenities available during flights. Recommendations or information about Copa Airlines' destinations and services. Connecting with a representative at Copa Airlines through ensures that your travel inquiries and concerns are met with efficiency and care. With their guidance, you can rest assured that you'll receive the support you need, whether it's regarding flight information, booking assistance, or any other travel-related matters. Don't hesitate to reach out through our platform whenever you need to talk to someone at Copa Airlines at 1 786 840-2672 or +1 (866) 897-5122 - their dedicated team is here to help make your travel experience as smooth and hassle-free as possible.

2 weeks, 6 days

1
0
0 0

How to Talk to a Live Person at Frontier Airlines?

by taige52＠netaxistech.com

Introducing a guide on connecting with a live person at Frontier Airlines . Ever found yourself stuck in the labyrinth of automated menus, desperately seeking a human touch? Look no further! This page is your beacon of hope, offering clear and concise steps to bypass the digital maze and speak directly to a real, empathetic Frontier Airlines representative. Is Frontier Airlines available 24/7? Frontier Airlines offers a reliable customer service experience that caters to its passengers' needs. Available 24/7, their dedicated team ensures that assistance is just a phone call away, regardless of the hour. By dialing +1 (801) 401-9000 or +1 (866) 897-5122, customers can reach out for support on a wide array of matters, from booking flights and managing reservations to addressing queries about travel policies. The round-the-clock availability of Frontier customer service underscores their commitment to providing continuous support. Whether it's a late-night travel emergency or a simple question during the early morning hours, passengers can count on getting the help they need. This constant accessibility offers peace of mind, knowing that Frontier Airlines is there to assist at any moment. And then, Frontier has been good in recognizing the importance of prompt and effective communication. Their customer service team is trained to handle diverse inquiries with professionalism and care, ensuring that every interaction leaves passengers feeling valued and heard. This dedication to service excellence is a key aspect of what makes Frontier Airlines a preferred choice for many travelers. How to speak with a Frontier Airlines customer service? Here's a step-by-step guide on how to speak with a Frontier Airlines customer service representative: Get your phone ready and dial either +1 (801) 401-9000 or +1 (866) 897-5122. These are the numbers to reach Frontier Airlines customer service. Sometimes, there might be a short wait before you're connected to a representative. Take a deep breath and hang in there. Once you're connected, you might hear a few options. Pay attention to them as they might guide you to the right department for your query. If prompted, press the number that corresponds to your reason for calling. This helps direct your call to the appropriate agent who can assist you better. When the representative picks up, introduce yourself and explain your reason for calling in a calm and friendly manner. Being polite goes a long way! Clearly explain what you need help with. Be if it's booking a flight, changing a reservation, or any other concern, provide as much detail as possible. The representative might ask you a few questions or provide instructions. Follow them carefully to resolve your issue efficiently. By following these quite simple steps, you will be able to speak with a Frontier Airlines customer service representative and get the assistance you need with ease. How many other ways of contacting Frontier are there apart from calling? Apart from calling +1 (801) 401-9000 or +1 (866) 897-5122, Frontier Airlines provides alternative means of contacting their customer service team, making assistance accessible through various channels. One such avenue is the Live Chat feature available on their website. Easily accessible from the Customer Service page, this option allows customers to engage in real-time conversations with a representative without the need for a phone call. By simply clicking on the "chat with us" tab, users can initiate a chat session and receive assistance promptly. Furthermore, Frontier Airlines offers the convenience of communicating via WhatsApp. Through the "Text on WhatsApp" option, passengers can connect with Frontier Airlines 24/7, leveraging the messaging platform to address their inquiries or concerns. This alternative mode of communication caters to individuals who prefer text-based interactions or those who may be unable to make a phone call at the moment. These additional contact methods showcase Frontier Airlines' commitment to providing diverse and accessible customer service options. Be if it's through live chat on the website or texting via WhatsApp, passengers have the flexibility to choose the communication channel that best suits their preferences and needs, guaranteeing a zero hassle experience when seeking assistance from the airline. Channeling through Frontier Airlines customer service landscape is now a breeze, thanks to this comprehensive guide. By providing multiple avenues for direct communication, including phone calls and live chat options, passengers can rest assured that their concerns will be addressed promptly and with care. Be if you are booking a flight, managing a reservation, or simply seeking assistance, dialing +1 (801) 401-9000 or +1 (866) 897-5122 is just the beginning of your journey to personalized customer service.

2 weeks, 6 days

1
0
0 0

How Can I Talk to Someone at Condor Airlines?

by taige52＠netaxistech.com

Trying to speak with someone at Condor Airlines and not sure where to start? This page will guide you through the most effective ways to get in touch with a live representative. Whether you prefer making a call, sending an email, or using instant messaging, Condor Airlines through offers several convenient methods to ensure your questions and concerns are promptly addressed. Calling Condor Airlines directly at 📞 1-866-897-5122. Whether you are trying to make a flight change, cancel your booking, ask about baggage, or resolve a booking issue, reaching a live agent can save you time, stress, and confusion. While automated systems are useful for simple tasks, some situations just need a human touch. How to talk to a live person at Condor Airlines? Talking to someone always makes things better and when it comes to getting help regarding your flights, you can reach out to Condor customer service which is available for you round-the-clock. Grab your phone and dial Condor Airlines phone number at +1-866-897-5122. Listen carefully to the menu options. When prompted, select your preferred language. Pay attention to the options provided. Choose the one that best matches your need, such as reservations, flight information, or general inquiries. When you hear the automated voice, press the key that connects you to a live agent. This is usually an option like “0” or “9”. Stay on the line. You might hear some music or promotional messages, but hang tight. A real person from Condor will be with you shortly. Have your flight information, booking reference, or any other relevant details ready to help the agent assist you more efficiently. Once connected, clearly state your question or concern. The friendly agent will be there to help you out. That’s it! Follow these easy steps, and you'll be talking to a real person at Condor Airlines in no time to get all the help you need regarding your flight trips. Can I contact Condor apart from calling? Absolutely, you have several options to get in touch with Condor Airlines beyond just calling +1-866-897-5122 . If you prefer a different mode of communication, sending an email can be a great alternative. You can reach out to Condor by emailing them at reservation.en(a)condor.com. This method allows you to detail your concerns or inquiries thoroughly and wait for a response at your convenience. It’s perfect for non-urgent matters or when you prefer written communication. For a more instant messaging approach, Condor also offers customer support through WhatsApp. You can contact them at +49 (0) 6171 69889 16 during their business hours from Monday to Friday, 9 AM to 10 PM CET, excluding public holidays. This option is fantastic if you’re on the go or need a quick answer without the wait time of a phone call. WhatsApp's accessibility and ease of use make it a popular choice for many travelers needing prompt assistance. These alternatives provide flexibility in how you choose to communicate with Condor Airlines, ensuring that your needs are met in a way that best suits your preferences. Whether it's through call, email, or a quick WhatsApp message, Condor is ready to assist you. What are the benefits that I can get via Condor Airlines customer service? Condor Airlines customer service offers a variety of benefits designed to enhance your travel experience and provide you with the support you need. One of the primary advantages is the convenience of immediate assistance. By calling the customer service numbers provided, you can quickly connect with a live agent who can address your questions, whether they pertain to flight reservations, changes, cancellations, or special requests. This direct interaction ensures that your concerns are handled promptly and effectively. And then, Condor customer service team is accessible through email, which is particularly beneficial for detailed inquiries or when you prefer written communication. This method allows you to thoroughly explain your situation and receive a considered response, ensuring clarity and comprehensive support. These various channels of communication ensure that you can reach Condor Airlines in the way that best suits your needs, providing flexibility and peace of mind. Whether you’re dealing with last-minute changes or planning ahead, Condor Airlines Customer Service is equipped to assist you with professionalism and care. Reaching out to Condor Airlines is straightforward with the multiple contact options available. These various methods ensure that Condor Airlines can cater to different preferences, making it easy for passengers to receive the support they need. No matter if it is a quick question or a more complex issue, Condor customer service team is equipped to handle it with professionalism and care, enhancing the overall travel experience.

2 weeks, 6 days

1
0
0 0

(866-432-8022) How to add a child to my Play reservation?

by taige52＠netaxistech.com

Yes, you can add a child to an already booked Play Airlines 1⁎866⁎432⁎8022 flight, but the process depends on the child’s age and ticket type. Steps to Add a Child to Your Booking Determine the Child’s Age Category • Lap Infant (Under 2 Years Old) Can travel for free on a parent/guardian’s lap on domestic flights. • You must call Play Airlines (866-432-8022) or add the infant via the Manage My Booking section on their website. • A birth certificate may be required at check-in. • Child with Seat (Over 2 Years Old or If You Prefer a Seat for an Infant) • A separate ticket must be purchased. • Call Play Airlines on 1⁎866⁎432⁎8022 to book and ensure the child is seated next to you. Contact Play Airlines • Call Customer Service: 1 (866-432-8022) • Use Live Chat: Available on the Play website • Airport Assistance: Visit the ticket counter if needed. Pay Any Applicable Fees • Lap infants are free on domestic flights but may incur taxes/fees on international flights. Ask customer support on (866-432-8022) • Adding a seat for a child will require paying the current fare for that seat.

2 weeks, 6 days

1
0
0 0

How do I add an infant to my already booked flight in EasyJet Airline?

by taige52＠netaxistech.com

To add an infant to your already booked EasyJet Airlines flight, follow these steps: Determine the Infant’s Travel Type • Lap Infant (Under 2 Years Old) – Travels free on domestic flights when seated on an adult’s lap. • Infant with a Seat – Requires a paid ticket and an FAA-approved car seat. Add the Infant to Your Booking call Call Customer Service: 1 (866-432-8022) • Option 1: Online (Manage My Booking) • Visit EasyJet Airlines website. • Click on “Manage My Booking” and enter your details. • Look for the option to add an infant and follow the prompts. • Option 2: Call EasyJet Airlines Customer Service • 📞 Phone: 1⁎866⁎432⁎8022 Speak with an agent to add the infant and confirm any applicable taxes/fees. Option 3: Add at the Airport Check-In Counter • If you were unable to add the infant online or via phone, visit the EasyJet ticket counter at the airport before your flight. Call Customer Service: 1 (866-432-8022) Provide Necessary Documents • Birth certificate or proof of age may be required at check-in. • For international travel, ensure the infant has a valid passport. Pay Any Applicable Fees • Domestic flights: Lap infants travel free (taxes may apply). • International flights: Fees and taxes may apply even for lap infants. • If purchasing a separate seat, you’ll pay the current fare for that seat.

2 weeks, 6 days

1
0
0 0

How to Speak to a Live Person Avelo Airlines: Tips and Tricks

by taige52＠netaxistech.com

Need to talk to a real person Avelo Airlines? Calling Avelo Airlines directly at 📞 1-866-897-5122. Whether you are trying to make a flight change, cancel your booking, ask about baggage, or resolve a booking issue, reaching a live agent can save you time, stress, and confusion. While automated systems are useful for simple tasks, some situations just need a human touch. In this guide, we will walk you through exactly how to reach a live person, what to prepare before calling, and alternate methods if the phone lines are busy. ☎️ First Things First: Call 1-866-897-5122 The most direct and reliable way to speak with a real Avelo Airlines representative is by calling 📞 1-866-897-5122. This is Frontier’s official customer service number and should be your go-to for: ✈️ Flight changes or cancellations 🧾 Refund or credit questions 🛄 Baggage issues 🔁 Name corrections 🛑 Check-in or boarding problems 💺 Seat selection and upgrades Pro Tip: When calling, try to do so during non-peak hours — early mornings or late evenings — to reduce your hold time. 🎧 How to Navigate the Automated Menu When you call 1-866-897-5122, you will first hear an automated system. To get through to a live person faster, follow these steps: Dial 1-866-897-5122 Wait for the automated greeting to begin Press “1” for English (or “2” for Spanish) Press “2” for existing reservations Press “0” to speak with an agent (you may need to press "0" more than once) 👉 If “0” does not work immediately, stay on the line. Sometimes the system transfers you to an agent after a brief wait without needing more input. If the lines are busy and you are placed on hold, do not hang up — wait times vary, but you will eventually reach someone. 🧾 What to Have Ready Before You Call To help the agent assist you faster, make sure you have the following details on hand: 📌 Your confirmation code or booking number 📌 The full name on the reservation 📌 Your flight date and destination 📌 Any relevant documents (ID, credit card, etc.) 📌 A notepad for writing down instructions or confirmation numbers If you are calling to fix a mistake or request a refund, be prepared to briefly explain the issue and possibly provide documentation via email upon request. ⏰ Best Times to Call 1-866-897-5122 Customer service lines can be busy, especially during: ⚠️ Holidays ⚠️ Severe weather or flight delays ⚠️ Early morning flight hours 🎯 For the best chance at a short wait, try calling during these times: 🕔 5:00 AM – 7:00 AM (EST) 🕘 9:00 PM – 11:00 PM (EST) 📅 Midweek (Tuesdays and Wednesdays) Avoid Mondays if possible — it is the busiest day for airlines. 🧑‍💻 Alternative Ways to Reach Avelo Airlines (If Phone Fails) If calling 📞 1-866-897-5122 does not work or you are stuck in a long queue, here are a few alternate ways to get help: 💬 1. Online Chat (Limited Availability) Visit www.flyfrontier.com Scroll down and look for the “Let’s Chat” option. This can connect you to a live agent or AI assistant, depending on availability. 📧 2. Email Support You can also submit a help request through their Customer Support Form online. Use this for non-urgent matters like refund requests or documentation review. 📱 3. Social Media Tweet or DM Avelo Airlines on platforms like Twitter/X (@FlyFrontier) or send a message via Facebook. Sometimes social media agents respond faster than the phone team during high-volume periods. 📲 4. Mobile App Download the Avelo Airlines App, log in, and navigate to “My Trips” or “Support” for quick options. While this will not guarantee a live agent, you might find answers to basic questions faster. ❗ Common Issues That Require a Live Agent While many tasks can be done online, certain problems are best resolved with a real person at 1-866-897-5122: 🛑 Double charges or billing issues 🔄 Complex flight changes involving multiple passengers 🛄 Lost or delayed baggage ✍️ Legal name changes (marriage, divorce, etc.) 🧑‍⚕️ Medical or accessibility needs during travel In these cases, avoid wasting time — call directly and ask for a live agent. 🚨 Beware of Fake Numbers and Scams Only use the official number: 📞 1-866-897-5122. Scammers often post fake “Frontier support” numbers online, asking for credit card info or login credentials. 🛡️ Never share your full credit card number or personal information with an unverified source. ✅ Final Thoughts Talking to a live person at an airline should not be this hard — but when it comes to Avelo Airlines, knowing the right steps and phone number makes all the difference. 🧠 Remember: Dial 📞 1-866-897-5122 Press 0 to reach a live agent Call during off-peak hours Have your booking info ready Use alternative methods if the line is too busy 💡 The sooner you reach out, the more options you'll have to resolve your issue. ✈️ Whether you are rebooking, fixing an error, or checking a flight, calling 1-866-897-5122 connects you with someone who can truly help.

2 weeks, 6 days

1
0
0 0

How to Get in Touch with a Live Representative Caribbean Airlines

by taige52＠netaxistech.com

Need to talk to a real person Caribbean Airlines? Calling Caribbean Airlines directly at 📞 1-866-897-5122. Whether you are trying to make a flight change, cancel your booking, ask about baggage, or resolve a booking issue, reaching a live agent can save you time, stress, and confusion. While automated systems are useful for simple tasks, some situations just need a human touch. In this guide, we will walk you through exactly how to reach a live person, what to prepare before calling, and alternate methods if the phone lines are busy. ☎️ First Things First: Call 1-866-897-5122 The most direct and reliable way to speak with a real Caribbean Airlines representative is by calling 📞 1-866-897-5122. This is Frontier’s official customer service number and should be your go-to for: ✈️ Flight changes or cancellations 🧾 Refund or credit questions 🛄 Baggage issues 🔁 Name corrections 🛑 Check-in or boarding problems 💺 Seat selection and upgrades Pro Tip: When calling, try to do so during non-peak hours — early mornings or late evenings — to reduce your hold time. 🎧 How to Navigate the Automated Menu When you call 1-866-897-5122, you will first hear an automated system. To get through to a live person faster, follow these steps: Dial 1-866-897-5122 Wait for the automated greeting to begin Press “1” for English (or “2” for Spanish) Press “2” for existing reservations Press “0” to speak with an agent (you may need to press "0" more than once) 👉 If “0” does not work immediately, stay on the line. Sometimes the system transfers you to an agent after a brief wait without needing more input. If the lines are busy and you are placed on hold, do not hang up — wait times vary, but you will eventually reach someone. 🧾 What to Have Ready Before You Call To help the agent assist you faster, make sure you have the following details on hand: 📌 Your confirmation code or booking number 📌 The full name on the reservation 📌 Your flight date and destination 📌 Any relevant documents (ID, credit card, etc.) 📌 A notepad for writing down instructions or confirmation numbers If you are calling to fix a mistake or request a refund, be prepared to briefly explain the issue and possibly provide documentation via email upon request. ⏰ Best Times to Call 1-866-897-5122 Customer service lines can be busy, especially during: ⚠️ Holidays ⚠️ Severe weather or flight delays ⚠️ Early morning flight hours 🎯 For the best chance at a short wait, try calling during these times: 🕔 5:00 AM – 7:00 AM (EST) 🕘 9:00 PM – 11:00 PM (EST) 📅 Midweek (Tuesdays and Wednesdays) Avoid Mondays if possible — it is the busiest day for airlines. 🧑‍💻 Alternative Ways to Reach Caribbean Airlines (If Phone Fails) If calling 📞 1-866-897-5122 does not work or you are stuck in a long queue, here are a few alternate ways to get help: 💬 1. Online Chat (Limited Availability) Visit www.flyfrontier.com Scroll down and look for the “Let’s Chat” option. This can connect you to a live agent or AI assistant, depending on availability. 📧 2. Email Support You can also submit a help request through their Customer Support Form online. Use this for non-urgent matters like refund requests or documentation review. 📱 3. Social Media Tweet or DM Caribbean Airlines on platforms like Twitter/X (@FlyFrontier) or send a message via Facebook. Sometimes social media agents respond faster than the phone team during high-volume periods. 📲 4. Mobile App Download the Caribbean Airlines App, log in, and navigate to “My Trips” or “Support” for quick options. While this will not guarantee a live agent, you might find answers to basic questions faster. ❗ Common Issues That Require a Live Agent While many tasks can be done online, certain problems are best resolved with a real person at 1-866-897-5122: 🛑 Double charges or billing issues 🔄 Complex flight changes involving multiple passengers 🛄 Lost or delayed baggage ✍️ Legal name changes (marriage, divorce, etc.) 🧑‍⚕️ Medical or accessibility needs during travel In these cases, avoid wasting time — call directly and ask for a live agent. 🚨 Beware of Fake Numbers and Scams Only use the official number: 📞 1-866-897-5122. Scammers often post fake “Frontier support” numbers online, asking for credit card info or login credentials. 🛡️ Never share your full credit card number or personal information with an unverified source. ✅ Final Thoughts Talking to a live person at an airline should not be this hard — but when it comes to Caribbean Airlines, knowing the right steps and phone number makes all the difference. 🧠 Remember: Dial 📞 1-866-897-5122 Press 0 to reach a live agent Call during off-peak hours Have your booking info ready Use alternative methods if the line is too busy 💡 The sooner you reach out, the more options you'll have to resolve your issue. ✈️ Whether you are rebooking, fixing an error, or checking a flight, calling 1-866-897-5122 connects you with someone who can truly help.

2 weeks, 6 days

1
0
0 0

[merged] um-disable-kasan_inline-when-static_link-is-selected.patch removed from -mm tree

by Andrew Morton

The quilt patch titled Subject: um: disable KASAN_INLINE when STATIC_LINK is selected has been removed from the -mm tree. Its filename was um-disable-kasan_inline-when-static_link-is-selected.patch This patch was dropped because it was merged into mainline or a subsystem tree ------------------------------------------------------ From: "Christophe Leroy (CS GROUP)" <chleroy(a)kernel.org> Subject: um: disable KASAN_INLINE when STATIC_LINK is selected Date: Sat, 29 Nov 2025 10:56:02 +0100 um doesn't support KASAN_INLINE together with STATIC_LINK. Instead of failing the build, disable KASAN_INLINE when STATIC_LINK is selected. Link: https://lkml.kernel.org/r/2620ab0bbba640b6237c50b9c0dca1c7d1142f5d.17644100… Fixes: 1e338f4d99e6 ("kasan: introduce ARCH_DEFER_KASAN and unify static key across modes") Signed-off-by: Christophe Leroy (CS GROUP) <chleroy(a)kernel.org> Reported-by: kernel test robot <lkp(a)intel.com> Closes: https://lore.kernel.org/oe-kbuild-all/202511290451.x9GZVJ1l-lkp@intel.com/ Cc: Alexander Potapenko <glider(a)google.com> Cc: Andrey Konovalov <andreyknvl(a)gmail.com> Cc: Andrey Ryabinin <ryabinin.a.a(a)gmail.com> Cc: Anton Ivanov <anton.ivanov(a)cambridgegreys.com> Cc: Dmitriy Vyukov <dvyukov(a)google.com> Cc: Johannes Berg <johannes(a)sipsolutions.net> Cc: Richard Weinberger <richard(a)nod.at> Cc: "Ritesh Harjani (IBM)" <ritesh.list(a)gmail.com> Cc: Sabyrzhan Tasbolatov <snovitoll(a)gmail.com> Cc: Vincenzo Frascino <vincenzo.frascino(a)arm.com> Cc: <stable(a)vger.kernel.org> Signed-off-by: Andrew Morton <akpm(a)linux-foundation.org> --- arch/um/Kconfig | 1 + arch/um/include/asm/kasan.h | 4 ---- 2 files changed, 1 insertion(+), 4 deletions(-) --- a/arch/um/include/asm/kasan.h~um-disable-kasan_inline-when-static_link-is-selected +++ a/arch/um/include/asm/kasan.h @@ -24,10 +24,6 @@ #ifdef CONFIG_KASAN void kasan_init(void); - -#if defined(CONFIG_STATIC_LINK) && defined(CONFIG_KASAN_INLINE) -#error UML does not work in KASAN_INLINE mode with STATIC_LINK enabled! -#endif #else static inline void kasan_init(void) { } #endif /* CONFIG_KASAN */ --- a/arch/um/Kconfig~um-disable-kasan_inline-when-static_link-is-selected +++ a/arch/um/Kconfig @@ -5,6 +5,7 @@ menu "UML-specific options" config UML bool default y + select ARCH_DISABLE_KASAN_INLINE if STATIC_LINK select ARCH_NEEDS_DEFER_KASAN if STATIC_LINK select ARCH_WANTS_DYNAMIC_TASK_STRUCT select ARCH_HAS_CACHE_LINE_SIZE _ Patches currently in -mm which might be from chleroy(a)kernel.org are

2 weeks, 6 days

1
0
0 0

[STATUS] stable/linux-6.6.y - 4791134e4aebe300af2b409dc550610ef69fae3e

by KernelCI bot

Hello, Status summary for stable/linux-6.6.y Dashboard: https://d.kernelci.org/c/stable/linux-6.6.y/4791134e4aebe300af2b409dc550610… giturl: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git branch: linux-6.6.y commit hash: 4791134e4aebe300af2b409dc550610ef69fae3e origin: maestro test start time: 2025-12-01 11:00:03.299000+00:00 Builds: 35 ✅ 4 ❌ 0 ⚠️ Boots: 94 ✅ 0 ❌ 0 ⚠️ Tests: 3919 ✅ 364 ❌ 1563 ⚠️ ### POSSIBLE REGRESSIONS No possible regressions observed. ### FIXED REGRESSIONS No fixed regressions observed. ### UNSTABLE TESTS Hardware: beaglebone-black > Config: multi_v7_defconfig - Architecture/compiler: arm/gcc-14 - ltp last run: https://d.kernelci.org/test/maestro:692ddc5ef5b8743b1f6f8407 history: > ❌ > ❌ > ✅ > ✅ > ❌ This branch has 4 pre-existing build issues. See details in the dashboard. Sent every day if there were changes in the past 24 hours. Legend: ✅ PASS ❌ FAIL ⚠️ INCONCLUSIVE -- This is an experimental report format. Please send feedback in! Talk to us at kernelci(a)lists.linux.dev Made with love by the KernelCI team - https://kernelci.org

2 weeks, 6 days

1
0
0 0

[STATUS] stable/linux-6.12.y - 318a47068f7b88de838518897500d7509e3fe205

by KernelCI bot

Hello, Status summary for stable/linux-6.12.y Dashboard: https://d.kernelci.org/c/stable/linux-6.12.y/318a47068f7b88de838518897500d7… giturl: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git branch: linux-6.12.y commit hash: 318a47068f7b88de838518897500d7509e3fe205 origin: maestro test start time: 2025-12-01 11:00:03.719000+00:00 Builds: 34 ✅ 5 ❌ 0 ⚠️ Boots: 189 ✅ 0 ❌ 0 ⚠️ Tests: 11205 ✅ 810 ❌ 2936 ⚠️ ### POSSIBLE REGRESSIONS No possible regressions observed. ### FIXED REGRESSIONS Hardware: beaglebone-black > Config: multi_v7_defconfig - Architecture/compiler: arm/gcc-14 - ltp last run: https://d.kernelci.org/test/maestro:692d842ef5b8743b1f6ef8d2 history: > ❌ > ❌ > ❌ > ✅ > ✅ ### UNSTABLE TESTS No unstable tests observed. This branch has 5 pre-existing build issues. See details in the dashboard. Sent every day if there were changes in the past 24 hours. Legend: ✅ PASS ❌ FAIL ⚠️ INCONCLUSIVE -- This is an experimental report format. Please send feedback in! Talk to us at kernelci(a)lists.linux.dev Made with love by the KernelCI team - https://kernelci.org

2 weeks, 6 days

1
0
0 0

¿Tu evaluación de desempeño es realmente objetiva?

by Luis Rodríguez

Evaluaciones de Desempeño Objetivas con Vorecol 360 Feedback body { margin: 0; padding: 0; font-family: Arial, Helvetica, sans-serif; font-size: 14px; color: #333333; background-color: #ffffff; } table { border-spacing: 0; width: 100%; max-width: 600px; margin: auto; } td { padding: 12px 20px; } a { color: #1a73e8; text-decoration: none; } .footer { font-size: 12px; color: #888888; text-align: center; padding-top: 10px; } Mejora tus evaluaciones de desempeño con feedback 360 real y automatizado. Hola, ¿Te has preguntado qué tan completas son tus evaluaciones de desempeño? En Vorecol 360 Feedback te ayudamos a implementar evaluaciones verdaderamente objetivas, recogiendo percepciones desde todas las direcciones: líderes, pares, colaboradores y autoevaluación. Lo que más valoran nuestros clientes de RRHH es que: Obtienen una visión completa y real del desempeño. Fomentan una cultura de feedback constructivo. Identifican oportunidades de desarrollo con mayor precisión. Automatizan todo el proceso con reportes claros y personalizables. Si estás buscando mejorar tus evaluaciones y fortalecer el desarrollo interno, te lo recomiendo muchísimo. Para más información puedes responder este correo o llamarme al número de abajo. Saludos, ------------------------ Atte.: Luis Rodríguez Ciudad de México: (55) 5018 0565 WhatsApp: +52 33 1607 2089 Si no deseas recibir más correos, haz clic aquí para darte de baja. Para remover su dirección de esta lista haga <a href="https://s1.arrobamail.com/unsuscribe.php?id=yiwtsrewiswqrrseup">click aquí</a>

2 weeks, 6 days

1
0
0 0

FAILED: patch "[PATCH] usb: gadget: udc: fix use-after-free in usb_gadget_state_work" failed to apply to 6.1-stable tree

by gregkh＠linuxfoundation.org

The patch below does not apply to the 6.1-stable tree. If someone wants it applied there, or to any other stable or longterm tree, then please email the backport, including the original git commit id to <stable(a)vger.kernel.org>. To reproduce the conflict and resubmit, you may use the following commands: git fetch https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/ linux-6.1.y git checkout FETCH_HEAD git cherry-pick -x baeb66fbd4201d1c4325074e78b1f557dff89b5b # <resolve conflicts, build, test, etc.> git commit -s git send-email --to '<stable(a)vger.kernel.org>' --in-reply-to '2025120122-submitter-flame-5478@gregkh' --subject-prefix 'PATCH 6.1.y' HEAD^.. Possible dependencies: thanks, greg k-h ------------------ original commit in Linus's tree ------------------ From baeb66fbd4201d1c4325074e78b1f557dff89b5b Mon Sep 17 00:00:00 2001 From: Jimmy Hu <hhhuuu(a)google.com> Date: Thu, 23 Oct 2025 05:49:45 +0000 Subject: [PATCH] usb: gadget: udc: fix use-after-free in usb_gadget_state_work A race condition during gadget teardown can lead to a use-after-free in usb_gadget_state_work(), as reported by KASAN: BUG: KASAN: invalid-access in sysfs_notify+0x2c/0xd0 Workqueue: events usb_gadget_state_work The fundamental race occurs because a concurrent event (e.g., an interrupt) can call usb_gadget_set_state() and schedule gadget->work at any time during the cleanup process in usb_del_gadget(). Commit 399a45e5237c ("usb: gadget: core: flush gadget workqueue after device removal") attempted to fix this by moving flush_work() to after device_del(). However, this does not fully solve the race, as a new work item can still be scheduled *after* flush_work() completes but before the gadget's memory is freed, leading to the same use-after-free. This patch fixes the race condition robustly by introducing a 'teardown' flag and a 'state_lock' spinlock to the usb_gadget struct. The flag is set during cleanup in usb_del_gadget() *before* calling flush_work() to prevent any new work from being scheduled once cleanup has commenced. The scheduling site, usb_gadget_set_state(), now checks this flag under the lock before queueing the work, thus safely closing the race window. Fixes: 5702f75375aa9 ("usb: gadget: udc-core: move sysfs_notify() to a workqueue") Cc: stable <stable(a)kernel.org> Signed-off-by: Jimmy Hu <hhhuuu(a)google.com> Link: https://patch.msgid.link/20251023054945.233861-1-hhhuuu@google.com Signed-off-by: Greg Kroah-Hartman <gregkh(a)linuxfoundation.org> diff --git a/drivers/usb/gadget/udc/core.c b/drivers/usb/gadget/udc/core.c index 694653761c44..8dbe79bdc0f9 100644 --- a/drivers/usb/gadget/udc/core.c +++ b/drivers/usb/gadget/udc/core.c @@ -1126,8 +1126,13 @@ static void usb_gadget_state_work(struct work_struct *work) void usb_gadget_set_state(struct usb_gadget *gadget, enum usb_device_state state) { + unsigned long flags; + + spin_lock_irqsave(&gadget->state_lock, flags); gadget->state = state; - schedule_work(&gadget->work); + if (!gadget->teardown) + schedule_work(&gadget->work); + spin_unlock_irqrestore(&gadget->state_lock, flags); trace_usb_gadget_set_state(gadget, 0); } EXPORT_SYMBOL_GPL(usb_gadget_set_state); @@ -1361,6 +1366,8 @@ static void usb_udc_nop_release(struct device *dev) void usb_initialize_gadget(struct device *parent, struct usb_gadget *gadget, void (*release)(struct device *dev)) { + spin_lock_init(&gadget->state_lock); + gadget->teardown = false; INIT_WORK(&gadget->work, usb_gadget_state_work); gadget->dev.parent = parent; @@ -1535,6 +1542,7 @@ EXPORT_SYMBOL_GPL(usb_add_gadget_udc); void usb_del_gadget(struct usb_gadget *gadget) { struct usb_udc *udc = gadget->udc; + unsigned long flags; if (!udc) return; @@ -1548,6 +1556,13 @@ void usb_del_gadget(struct usb_gadget *gadget) kobject_uevent(&udc->dev.kobj, KOBJ_REMOVE); sysfs_remove_link(&udc->dev.kobj, "gadget"); device_del(&gadget->dev); + /* + * Set the teardown flag before flushing the work to prevent new work + * from being scheduled while we are cleaning up. + */ + spin_lock_irqsave(&gadget->state_lock, flags); + gadget->teardown = true; + spin_unlock_irqrestore(&gadget->state_lock, flags); flush_work(&gadget->work); ida_free(&gadget_id_numbers, gadget->id_number); cancel_work_sync(&udc->vbus_work); diff --git a/include/linux/usb/gadget.h b/include/linux/usb/gadget.h index 3aaf19e77558..8285b19a25e0 100644 --- a/include/linux/usb/gadget.h +++ b/include/linux/usb/gadget.h @@ -376,6 +376,9 @@ struct usb_gadget_ops { * can handle. The UDC must support this and all slower speeds and lower * number of lanes. * @state: the state we are now (attached, suspended, configured, etc) + * @state_lock: Spinlock protecting the `state` and `teardown` members. + * @teardown: True if the device is undergoing teardown, used to prevent + * new work from being scheduled during cleanup. * @name: Identifies the controller hardware type. Used in diagnostics * and sometimes configuration. * @dev: Driver model state for this abstract device. @@ -451,6 +454,8 @@ struct usb_gadget { enum usb_ssp_rate max_ssp_rate; enum usb_device_state state; + spinlock_t state_lock; + bool teardown; const char *name; struct device dev; unsigned isoch_delay;

2 weeks, 6 days

2
2
0 0

FAILED: patch "[PATCH] usb: gadget: udc: fix use-after-free in usb_gadget_state_work" failed to apply to 6.6-stable tree

by gregkh＠linuxfoundation.org

The patch below does not apply to the 6.6-stable tree. If someone wants it applied there, or to any other stable or longterm tree, then please email the backport, including the original git commit id to <stable(a)vger.kernel.org>. To reproduce the conflict and resubmit, you may use the following commands: git fetch https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/ linux-6.6.y git checkout FETCH_HEAD git cherry-pick -x baeb66fbd4201d1c4325074e78b1f557dff89b5b # <resolve conflicts, build, test, etc.> git commit -s git send-email --to '<stable(a)vger.kernel.org>' --in-reply-to '2025120122-shelter-unlit-af6a@gregkh' --subject-prefix 'PATCH 6.6.y' HEAD^.. Possible dependencies: thanks, greg k-h ------------------ original commit in Linus's tree ------------------ From baeb66fbd4201d1c4325074e78b1f557dff89b5b Mon Sep 17 00:00:00 2001 From: Jimmy Hu <hhhuuu(a)google.com> Date: Thu, 23 Oct 2025 05:49:45 +0000 Subject: [PATCH] usb: gadget: udc: fix use-after-free in usb_gadget_state_work A race condition during gadget teardown can lead to a use-after-free in usb_gadget_state_work(), as reported by KASAN: BUG: KASAN: invalid-access in sysfs_notify+0x2c/0xd0 Workqueue: events usb_gadget_state_work The fundamental race occurs because a concurrent event (e.g., an interrupt) can call usb_gadget_set_state() and schedule gadget->work at any time during the cleanup process in usb_del_gadget(). Commit 399a45e5237c ("usb: gadget: core: flush gadget workqueue after device removal") attempted to fix this by moving flush_work() to after device_del(). However, this does not fully solve the race, as a new work item can still be scheduled *after* flush_work() completes but before the gadget's memory is freed, leading to the same use-after-free. This patch fixes the race condition robustly by introducing a 'teardown' flag and a 'state_lock' spinlock to the usb_gadget struct. The flag is set during cleanup in usb_del_gadget() *before* calling flush_work() to prevent any new work from being scheduled once cleanup has commenced. The scheduling site, usb_gadget_set_state(), now checks this flag under the lock before queueing the work, thus safely closing the race window. Fixes: 5702f75375aa9 ("usb: gadget: udc-core: move sysfs_notify() to a workqueue") Cc: stable <stable(a)kernel.org> Signed-off-by: Jimmy Hu <hhhuuu(a)google.com> Link: https://patch.msgid.link/20251023054945.233861-1-hhhuuu@google.com Signed-off-by: Greg Kroah-Hartman <gregkh(a)linuxfoundation.org> diff --git a/drivers/usb/gadget/udc/core.c b/drivers/usb/gadget/udc/core.c index 694653761c44..8dbe79bdc0f9 100644 --- a/drivers/usb/gadget/udc/core.c +++ b/drivers/usb/gadget/udc/core.c @@ -1126,8 +1126,13 @@ static void usb_gadget_state_work(struct work_struct *work) void usb_gadget_set_state(struct usb_gadget *gadget, enum usb_device_state state) { + unsigned long flags; + + spin_lock_irqsave(&gadget->state_lock, flags); gadget->state = state; - schedule_work(&gadget->work); + if (!gadget->teardown) + schedule_work(&gadget->work); + spin_unlock_irqrestore(&gadget->state_lock, flags); trace_usb_gadget_set_state(gadget, 0); } EXPORT_SYMBOL_GPL(usb_gadget_set_state); @@ -1361,6 +1366,8 @@ static void usb_udc_nop_release(struct device *dev) void usb_initialize_gadget(struct device *parent, struct usb_gadget *gadget, void (*release)(struct device *dev)) { + spin_lock_init(&gadget->state_lock); + gadget->teardown = false; INIT_WORK(&gadget->work, usb_gadget_state_work); gadget->dev.parent = parent; @@ -1535,6 +1542,7 @@ EXPORT_SYMBOL_GPL(usb_add_gadget_udc); void usb_del_gadget(struct usb_gadget *gadget) { struct usb_udc *udc = gadget->udc; + unsigned long flags; if (!udc) return; @@ -1548,6 +1556,13 @@ void usb_del_gadget(struct usb_gadget *gadget) kobject_uevent(&udc->dev.kobj, KOBJ_REMOVE); sysfs_remove_link(&udc->dev.kobj, "gadget"); device_del(&gadget->dev); + /* + * Set the teardown flag before flushing the work to prevent new work + * from being scheduled while we are cleaning up. + */ + spin_lock_irqsave(&gadget->state_lock, flags); + gadget->teardown = true; + spin_unlock_irqrestore(&gadget->state_lock, flags); flush_work(&gadget->work); ida_free(&gadget_id_numbers, gadget->id_number); cancel_work_sync(&udc->vbus_work); diff --git a/include/linux/usb/gadget.h b/include/linux/usb/gadget.h index 3aaf19e77558..8285b19a25e0 100644 --- a/include/linux/usb/gadget.h +++ b/include/linux/usb/gadget.h @@ -376,6 +376,9 @@ struct usb_gadget_ops { * can handle. The UDC must support this and all slower speeds and lower * number of lanes. * @state: the state we are now (attached, suspended, configured, etc) + * @state_lock: Spinlock protecting the `state` and `teardown` members. + * @teardown: True if the device is undergoing teardown, used to prevent + * new work from being scheduled during cleanup. * @name: Identifies the controller hardware type. Used in diagnostics * and sometimes configuration. * @dev: Driver model state for this abstract device. @@ -451,6 +454,8 @@ struct usb_gadget { enum usb_ssp_rate max_ssp_rate; enum usb_device_state state; + spinlock_t state_lock; + bool teardown; const char *name; struct device dev; unsigned isoch_delay;

2 weeks, 6 days

2
2
0 0

FAILED: patch "[PATCH] usb: gadget: udc: fix use-after-free in usb_gadget_state_work" failed to apply to 6.12-stable tree

by gregkh＠linuxfoundation.org

The patch below does not apply to the 6.12-stable tree. If someone wants it applied there, or to any other stable or longterm tree, then please email the backport, including the original git commit id to <stable(a)vger.kernel.org>. To reproduce the conflict and resubmit, you may use the following commands: git fetch https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/ linux-6.12.y git checkout FETCH_HEAD git cherry-pick -x baeb66fbd4201d1c4325074e78b1f557dff89b5b # <resolve conflicts, build, test, etc.> git commit -s git send-email --to '<stable(a)vger.kernel.org>' --in-reply-to '2025120121-sift-shiny-dd51@gregkh' --subject-prefix 'PATCH 6.12.y' HEAD^.. Possible dependencies: thanks, greg k-h ------------------ original commit in Linus's tree ------------------ From baeb66fbd4201d1c4325074e78b1f557dff89b5b Mon Sep 17 00:00:00 2001 From: Jimmy Hu <hhhuuu(a)google.com> Date: Thu, 23 Oct 2025 05:49:45 +0000 Subject: [PATCH] usb: gadget: udc: fix use-after-free in usb_gadget_state_work A race condition during gadget teardown can lead to a use-after-free in usb_gadget_state_work(), as reported by KASAN: BUG: KASAN: invalid-access in sysfs_notify+0x2c/0xd0 Workqueue: events usb_gadget_state_work The fundamental race occurs because a concurrent event (e.g., an interrupt) can call usb_gadget_set_state() and schedule gadget->work at any time during the cleanup process in usb_del_gadget(). Commit 399a45e5237c ("usb: gadget: core: flush gadget workqueue after device removal") attempted to fix this by moving flush_work() to after device_del(). However, this does not fully solve the race, as a new work item can still be scheduled *after* flush_work() completes but before the gadget's memory is freed, leading to the same use-after-free. This patch fixes the race condition robustly by introducing a 'teardown' flag and a 'state_lock' spinlock to the usb_gadget struct. The flag is set during cleanup in usb_del_gadget() *before* calling flush_work() to prevent any new work from being scheduled once cleanup has commenced. The scheduling site, usb_gadget_set_state(), now checks this flag under the lock before queueing the work, thus safely closing the race window. Fixes: 5702f75375aa9 ("usb: gadget: udc-core: move sysfs_notify() to a workqueue") Cc: stable <stable(a)kernel.org> Signed-off-by: Jimmy Hu <hhhuuu(a)google.com> Link: https://patch.msgid.link/20251023054945.233861-1-hhhuuu@google.com Signed-off-by: Greg Kroah-Hartman <gregkh(a)linuxfoundation.org> diff --git a/drivers/usb/gadget/udc/core.c b/drivers/usb/gadget/udc/core.c index 694653761c44..8dbe79bdc0f9 100644 --- a/drivers/usb/gadget/udc/core.c +++ b/drivers/usb/gadget/udc/core.c @@ -1126,8 +1126,13 @@ static void usb_gadget_state_work(struct work_struct *work) void usb_gadget_set_state(struct usb_gadget *gadget, enum usb_device_state state) { + unsigned long flags; + + spin_lock_irqsave(&gadget->state_lock, flags); gadget->state = state; - schedule_work(&gadget->work); + if (!gadget->teardown) + schedule_work(&gadget->work); + spin_unlock_irqrestore(&gadget->state_lock, flags); trace_usb_gadget_set_state(gadget, 0); } EXPORT_SYMBOL_GPL(usb_gadget_set_state); @@ -1361,6 +1366,8 @@ static void usb_udc_nop_release(struct device *dev) void usb_initialize_gadget(struct device *parent, struct usb_gadget *gadget, void (*release)(struct device *dev)) { + spin_lock_init(&gadget->state_lock); + gadget->teardown = false; INIT_WORK(&gadget->work, usb_gadget_state_work); gadget->dev.parent = parent; @@ -1535,6 +1542,7 @@ EXPORT_SYMBOL_GPL(usb_add_gadget_udc); void usb_del_gadget(struct usb_gadget *gadget) { struct usb_udc *udc = gadget->udc; + unsigned long flags; if (!udc) return; @@ -1548,6 +1556,13 @@ void usb_del_gadget(struct usb_gadget *gadget) kobject_uevent(&udc->dev.kobj, KOBJ_REMOVE); sysfs_remove_link(&udc->dev.kobj, "gadget"); device_del(&gadget->dev); + /* + * Set the teardown flag before flushing the work to prevent new work + * from being scheduled while we are cleaning up. + */ + spin_lock_irqsave(&gadget->state_lock, flags); + gadget->teardown = true; + spin_unlock_irqrestore(&gadget->state_lock, flags); flush_work(&gadget->work); ida_free(&gadget_id_numbers, gadget->id_number); cancel_work_sync(&udc->vbus_work); diff --git a/include/linux/usb/gadget.h b/include/linux/usb/gadget.h index 3aaf19e77558..8285b19a25e0 100644 --- a/include/linux/usb/gadget.h +++ b/include/linux/usb/gadget.h @@ -376,6 +376,9 @@ struct usb_gadget_ops { * can handle. The UDC must support this and all slower speeds and lower * number of lanes. * @state: the state we are now (attached, suspended, configured, etc) + * @state_lock: Spinlock protecting the `state` and `teardown` members. + * @teardown: True if the device is undergoing teardown, used to prevent + * new work from being scheduled during cleanup. * @name: Identifies the controller hardware type. Used in diagnostics * and sometimes configuration. * @dev: Driver model state for this abstract device. @@ -451,6 +454,8 @@ struct usb_gadget { enum usb_ssp_rate max_ssp_rate; enum usb_device_state state; + spinlock_t state_lock; + bool teardown; const char *name; struct device dev; unsigned isoch_delay;

2 weeks, 6 days

2
2
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

Linux-stable-mirror