From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) (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 E6E92395DA0 for ; Tue, 3 Feb 2026 08:44:37 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=170.10.133.124 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1770108279; cv=none; b=puAchDJIQZXDJIZGQIrjKg1qGPokX57HMOEipzTaAOgWPNgdlqX9Dj3tvpiBUrH6qdr0CKV3hjj865gDzDnm9yq6fUtH828JgfU3IW5JOgkvEl80vTK/z5jKfB/QU1tuyjsqbUmAXW3QaAMmLCdj9zY9ib/PYDcT0Amdb8Hjl5s= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1770108279; c=relaxed/simple; bh=c/MlIGyRe6Ua1hKekR0FD9JRU3veBk2Rq2u+/LF8An0=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=pYpHkj17g6rc5yXznvS+heGM8M4tLhVjHnJcB8w1I4JKn3zdlvYeMtzsGDP0csXSqV0HYCuT3vuThhw9XLOmfP+o5e1qvYoSJhjvvd2LNXGhlSCIldHN4fz5p+x0kPwzhh/BfMgBRwTAOnKsZa4TfucTxV3IG/JLiHHJ2/UchuQ= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=redhat.com; spf=pass smtp.mailfrom=redhat.com; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b=coGhzWOP; dkim=pass (2048-bit key) header.d=redhat.com header.i=@redhat.com header.b=sv6+gmwx; arc=none smtp.client-ip=170.10.133.124 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=redhat.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=redhat.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="coGhzWOP"; dkim=pass (2048-bit key) header.d=redhat.com header.i=@redhat.com header.b="sv6+gmwx" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1770108276; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=VgHLoc4JJmVQ+DPngHL651kkYSwBeL/ZVkdO3ynZe2Q=; b=coGhzWOPrCwEE4yar3gOZVA+VELdXH17SpVMDjnG7Ff6fmegsO2Qf4m+rwVnnZhFZSqBIU xbClAs1XvG4xOg0Ngnp2ok2+xIi30QRYaReqsiJ2yzSp3AhN9QctYGmfDlXK8WVp6Nwl+h RLhsJD81V+649b5OhvkAsR5EUofY0bk= Received: from mail-wr1-f69.google.com (mail-wr1-f69.google.com [209.85.221.69]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-400-Yuy34BeoMcq61FN9v0kkHw-1; Tue, 03 Feb 2026 03:44:35 -0500 X-MC-Unique: Yuy34BeoMcq61FN9v0kkHw-1 X-Mimecast-MFC-AGG-ID: Yuy34BeoMcq61FN9v0kkHw_1770108274 Received: by mail-wr1-f69.google.com with SMTP id ffacd0b85a97d-430fcf10287so4920550f8f.0 for ; Tue, 03 Feb 2026 00:44:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=google; t=1770108274; x=1770713074; darn=vger.kernel.org; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=VgHLoc4JJmVQ+DPngHL651kkYSwBeL/ZVkdO3ynZe2Q=; b=sv6+gmwxcaS4rSTI5aPgrABvTFXRxbk7YnuehxEVfptDh446D544wBE/8K+HMSgGto 3rBmY5uAflwOBWTxML8DYa2835TZ6RtrWuK5NadnEmayEZchIyY9iRp2xNFfjtsfJBgK VCxCwxxVIl8w28P69AmG7+6e7NJU21QMmeX0q8rFNFOFpFhelkNqgOLIOP3ZH9v0z4Pi RlRT9mk6i/j6etlDDW9ecLkZBFnX7+cjiuzPBiT/R5nL26p2bn8cc96Dn5gZnrDot+5M wkywuwEQMp0pWr+L2hIwclq0ulANHO4M/fa7ZvImrVfahWC6S0e5FasY5CQBGoVFHdWJ b8gg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1770108274; x=1770713074; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:user-agent:mime-version:date:message-id :x-gm-gg:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=VgHLoc4JJmVQ+DPngHL651kkYSwBeL/ZVkdO3ynZe2Q=; b=RUj+eNdUKckbbsA+QcUwygWJXktLESsoa/1b2GC9BWFXiA36MBTPSPtc9s40gzjTtR bR16oY/S13rK+36rkiRaNx+1jp6/MrcY1VKzO6Ban0I32/V93NTjHoA6WWuoRuH3XrRy LFH+2/k8GwJmMyZOhWmPRjHQN0+JHL/Q4kk4GWCTAy46TxZXCxsuNX6fnrA9Ehx2ns26 eH0OjiYUs65BS50tZNA1Tyk9ozxSFqjRdpmbw3JrrgXy6U8P/pX4LV3mwl5uGQ8Hj7Nd fdsASGyC93O0OEfJ4x8IOafw1lD1Y5gK5S4nMRsUDyy0qNgCmVemPU08LdPTYfMjb6Sv +Tnw== X-Forwarded-Encrypted: i=1; AJvYcCUKPSPssnd9ID040azmCiRkEEKS1ZNbNScqwP0vqSpKMOcIOGEf/d1Y+gQ8Qn1U4QbJWfqd5cpdKb0pNds=@vger.kernel.org X-Gm-Message-State: AOJu0Yw9JrnzcgX3XGcIPo9M1EfEryhPFYd+KMh6iZRXnv7yhHDqC1MO Yqk9E5d5LyWTmfXNVREpD+f4kUCHeIqcZF/qBZhOiEurA0rY1iKjvJWfUQby22gfgjzkdPSbQWj 5p5SUWaQxgoNEu711GETTVn2TvRMof+5sHIfYNhYQaIG+ZRISg7dPIQVLbWC2aqqidg== X-Gm-Gg: AZuq6aKnoz2aAeV612ucWGeBczWTPIcF/woe3VMc2Q0G5XxiHLkRa3ZtT/2Owu1qmOK vtAgyOqzpYCsumZiB2tuhu+PDH8pX41C4cRgZA3XLAo/Ed0167XHnFxaPUa/q3TSxcXo+3utgPA L653uVbgNfVA/9eNdYQaQvVhunomgF2G1bcJAetuYJLguTCBUVOautFf02RbTOk1StjjnmF/O6z zrqvQZzjMfeB3ogAUa9kk6OcBRTHi/JcmT8ZtRxV1HXWV48VlydxQtx6H/L+fu1QZhK93BrPno3 J7DW5OzWFEyRmUKOgSa0PO6+XDqg8NjQ7IpJ+u0chC43ck/byfpD3ddOXOkQE7cN+7zZT5L+SLO uyKMKt8At X-Received: by 2002:a05:6000:401f:b0:430:f241:a11f with SMTP id ffacd0b85a97d-435f3aaa5aemr19352650f8f.30.1770108274172; Tue, 03 Feb 2026 00:44:34 -0800 (PST) X-Received: by 2002:a05:6000:401f:b0:430:f241:a11f with SMTP id ffacd0b85a97d-435f3aaa5aemr19352628f8f.30.1770108273800; Tue, 03 Feb 2026 00:44:33 -0800 (PST) Received: from [192.168.2.83] ([46.175.183.46]) by smtp.gmail.com with ESMTPSA id ffacd0b85a97d-435e10f82aesm52194011f8f.19.2026.02.03.00.44.32 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 03 Feb 2026 00:44:33 -0800 (PST) Message-ID: <14cb0b22-ec39-43e4-a35b-22ad558b2e34@redhat.com> Date: Tue, 3 Feb 2026 09:44:31 +0100 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [Intel-wired-lan] [PATCH net] iavf: fix deadlock in reset handling To: Jacob Keller , Jakub Kicinski Cc: ivecera@redhat.com, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, Andrew Lunn , Eric Dumazet , Stanislav Fomichev , Tony Nguyen , Przemek Kitszel , intel-wired-lan@lists.osuosl.org, Paolo Abeni , "David S. Miller" References: <20260202084820.260033-1-poros@redhat.com> <20260202155813.3f8fbc27@kernel.org> Content-Language: en-US From: Petr Oros In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit On 2/3/26 02:00, Jacob Keller wrote: > > > On 2/2/2026 3:58 PM, Jakub Kicinski wrote: >> On Mon,  2 Feb 2026 09:48:20 +0100 Petr Oros wrote: >>> +    netdev_unlock(netdev); >>> +    ret = wait_event_interruptible_timeout(adapter->reset_waitqueue, >>> + !iavf_is_reset_in_progress(adapter), >>> +                           msecs_to_jiffies(5000)); >>> +    netdev_lock(netdev); >> >> Dropping locks taken by the core around the driver callback >> is obviously unacceptable. SMH. > > Right. It seems like the correct fix is to either a) have reset take > and hold the netdev lock (now that its distinct from the global RTNL > lock) or b) refactor reset so that it can defer any of the netdev > related stuff somehow. > I modeled this after the existing pattern in iavf_close() (ndo_stop), which also temporarily releases the netdev instance lock taken by the core to wait for an async operation to complete: static int iavf_close(struct net_device *netdev) {         netdev_assert_locked(netdev);         ...         iavf_down(adapter);         iavf_change_state(adapter, __IAVF_DOWN_PENDING);         iavf_free_traffic_irqs(adapter);         netdev_unlock(netdev);         status = wait_event_timeout(adapter->down_waitqueue,                                     adapter->state == __IAVF_DOWN,                                     msecs_to_jiffies(500));         if (!status)                 netdev_warn(netdev, "Device resources not yet released\n");         netdev_lock(netdev);         ... } This was introduced by commit 120f28a6f314fe ("iavf: get rid of the crit lock"), and ndo_stop is called with netdev instance lock held by the core just like ndo_change_mtu is. Could you clarify why the unlock-wait-lock pattern is acceptable in ndo_stop but not here?