From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-13.8 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, INCLUDES_CR_TRAILER,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED, USER_AGENT_GIT autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id E9209C4361B for ; Thu, 17 Dec 2020 13:05:30 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 8DF812389E for ; Thu, 17 Dec 2020 13:05:30 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727294AbgLQNFO (ORCPT ); Thu, 17 Dec 2020 08:05:14 -0500 Received: from smtp-fw-9103.amazon.com ([207.171.188.200]:37055 "EHLO smtp-fw-9103.amazon.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726613AbgLQNFO (ORCPT ); Thu, 17 Dec 2020 08:05:14 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=amazon.com; i=@amazon.com; q=dns/txt; s=amazon201209; t=1608210314; x=1639746314; h=from:to:cc:subject:date:message-id:in-reply-to: mime-version; bh=bE7D90KlVd4iO8CcTy0iOt4Oce3p/63L3jHohC3ijas=; b=Xrx757XdpPIj1FQ5Xo4VunlLfui5WfgxwZ+cm8szEJPmhZA1SAgYw9X3 yr/fEqO/HEskUHFHerhzV+6SawdmhAComfuxrp9q+7y6w5gyel2sgQ6u+ qZ/WjkAU27IZOV7qcMh6e8z1xR2zldXTFbb/eLTV60rBwdL6RHq6buFMn Y=; X-IronPort-AV: E=Sophos;i="5.78,428,1599523200"; d="scan'208";a="903914151" Received: from sea32-co-svc-lb4-vlan3.sea.corp.amazon.com (HELO email-inbound-relay-1a-7d76a15f.us-east-1.amazon.com) ([10.47.23.38]) by smtp-border-fw-out-9103.sea19.amazon.com with ESMTP; 17 Dec 2020 13:04:24 +0000 Received: from EX13D31EUA004.ant.amazon.com (iad12-ws-svc-p26-lb9-vlan2.iad.amazon.com [10.40.163.34]) by email-inbound-relay-1a-7d76a15f.us-east-1.amazon.com (Postfix) with ESMTPS id 4C3A7A209E; Thu, 17 Dec 2020 13:04:24 +0000 (UTC) Received: from u3f2cd687b01c55.ant.amazon.com (10.43.161.68) by EX13D31EUA004.ant.amazon.com (10.43.165.161) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Thu, 17 Dec 2020 13:04:18 +0000 From: SeongJae Park To: SeongJae Park CC: , SeongJae Park , , , , , , , , "Author Redacted" Subject: Re: [PATCH 2/5] xen/xenbus: Add 'will_handle' callback support in xenbus_watch_path() Date: Thu, 17 Dec 2020 14:04:03 +0100 Message-ID: <20201217130403.12531-1-sjpark@amazon.com> X-Mailer: git-send-email 2.17.1 In-Reply-To: <20201217081727.8253-3-sjpark@amazon.com> MIME-Version: 1.0 Content-Type: text/plain X-Originating-IP: [10.43.161.68] X-ClientProxiedBy: EX13D49UWB003.ant.amazon.com (10.43.163.121) To EX13D31EUA004.ant.amazon.com (10.43.165.161) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 17 Dec 2020 09:17:24 +0100 SeongJae Park wrote: > From: SeongJae Park > > Some code does not directly make 'xenbus_watch' object and call > 'register_xenbus_watch()' but use 'xenbus_watch_path()' instead. This > commit adds support of 'will_handle' callback in the > 'xenbus_watch_path()' and it's wrapper, 'xenbus_watch_pathfmt()'. > > This is part of XSA-349 > > This is upstream commit 2e85d32b1c865bec703ce0c962221a5e955c52c2 > > Cc: stable@vger.kernel.org > Signed-off-by: SeongJae Park > Reported-by: Michael Kurth > Reported-by: Pawel Wieczorkiewicz > Signed-off-by: Author Redacted Juergen found this wrong line (thank you, Juergen!). I will remove the lines from the patches and send 2nd version soon. Thanks, SeongJae Park