From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 98F423AA1BD; Wed, 29 Apr 2026 21:41:42 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1777498902; cv=none; b=S5tUqYbUReb/WoTJiQPrNAu6VoJKDJkhGxikT/v89pQpyy+w2m9tD1Qh3O4fQyu41rMJ6mDHOwbCvTxeVkztpTzSofqwtE35VS55w+rU/ZJ0u8KUZPIRdJM/b/eNTgwUwLtVGRygz/9eXK4VBvluMJdzV2I7LeCS+xpPKlCRovw= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1777498902; c=relaxed/simple; bh=ui1rqtgLpeGn5C+ZcFXl/6vBB8zvioe6IQ0674oNrzs=; h=Mime-Version:Content-Type:Date:Message-Id:Subject:Cc:To:From: References:In-Reply-To; b=a96K2gTqda8aE2s0HBKA4b9aqu/5BlndD9l4cvFOSy0S6VS4H16AwEXI6FjevWIiaNxvQJ0m8Pz8C6IcKjdEC0fCnxTQElP7eylkSFgvZX4xWrH2iPF788ECwRCY9pXfGjYtQF3b3CoA9k/kVhsJqNwNBSBpuIfF5bBJTYqCbDw= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=CNz85NnZ; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="CNz85NnZ" Received: by smtp.kernel.org (Postfix) with ESMTPSA id E2AB1C19425; Wed, 29 Apr 2026 21:41:39 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1777498902; bh=ui1rqtgLpeGn5C+ZcFXl/6vBB8zvioe6IQ0674oNrzs=; h=Date:Subject:Cc:To:From:References:In-Reply-To:From; b=CNz85NnZ5JtP76f0yGy2+EmSGdo+mqxKdWl5iDjoNq0hFIGD/UdxytniPBUaaYurz qhayyg32cyz6R9f7xxyI7OK+0PAUPP6VMcQvnaNj9Eta8XVSl+Cy8aHnJvUMH9d2nV H7t91usWG6HkbWKcUkgBVjfzJZ9ujSVxaYPv5P6h8kS9rZhPpNvnryBXLNr7qR4i9D F3gjgfqy6SCpCsF6mXWfhsegCTDasmvy5ZxY9ADHr0UY3ZWvE70yOgo4/+aYZoq7xK YCTJEU2FekcjLBRcE+auBVr7aqgjGwY0HqrDIIm/dS6rRdqkCHjrW6H0VwFxfSk18k KfBI3ICN9o/PA== Precedence: bulk X-Mailing-List: stable@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 Date: Wed, 29 Apr 2026 23:41:38 +0200 Message-Id: Subject: Re: [PATCH] drivers: base: Set mod->async_probe_requested if needed Cc: "Greg Kroah-Hartman" , "Rafael J . Wysocki" , , "Luis Chamberlain" , "Petr Pavlu" , "Daniel Gomez" , "Sami Tolvanen" , "Aaron Tomlin" , "Igor Pylypiv" , "Chung-Kai Mei" , "Luis R. Rodriguez" , To: "Bart Van Assche" From: "Danilo Krummrich" References: <20260407160511.56289-1-bvanassche@acm.org> <2fc4a2af-a4bb-4797-87eb-e95b835aa673@acm.org> In-Reply-To: <2fc4a2af-a4bb-4797-87eb-e95b835aa673@acm.org> (Cc: Luis) On Tue Apr 28, 2026 at 9:39 PM CEST, Bart Van Assche wrote: > On 4/28/26 11:22 AM, Danilo Krummrich wrote: >> What if userspace did explicitly pass async_probe=3D0? > > Does this mean that what the user has configured should take precedence, > as in the untested patch below? Yes, but my concern actually goes beyond that (sorry for not expressing thi= s properly right away). I think the whole reason the async_probe module parameter exists in the fir= st place is because userspace may rely on the devices being handled by the mod= ule to be available directly after returning from the syscall. Even worse, with this patch we would make this user facing behavior depende= nt on an implementation detail of the driver, i.e. whether it chooses to opt into PROBE_PREFER_ASYNCHRONOUS.