From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-pl1-f176.google.com (mail-pl1-f176.google.com [209.85.214.176]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id A7C0576034 for ; Thu, 28 Nov 2024 03:54:06 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.214.176 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1732766048; cv=none; b=Q1/4rWAFEEV1qTRGuL7QTLWYHN4LZSu9YwoX6vxznnkNvYRw/mpc5nLyr+NxvO4b5kFxiT5BmzA7ZpKR2UrekOn1N0KD0TVFsFZx3WaV29uSUVymYILE9jlUO5SYBVRYjx/OCkUg1vO0q+OXf8sE8VqiabYhMpogQXoN947zEj4= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1732766048; c=relaxed/simple; bh=VmRHmqJGZNsVUqgTQtXEBy3bZGPIe6ah/oVVl+q2Fdc=; h=Date:From:To:Cc:Subject:Message-ID:MIME-Version:Content-Type: Content-Disposition; b=lYNY8cvEJBOw8rIWM1Ncg3iiCLXiTrrwn5mzPISRS+mpSHj/Jjpo63JTcXMx4kMqFZyDsCcpmTLzDbyGb0L44/9Du35+rb/bejRlRvyZvqto7iKT2Oz0Mkxws+5Q3Ii8gHb+McEEMtOExefjGlFhmiQSggCFJiIPH60I7SFpJRY= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=chromium.org; spf=pass smtp.mailfrom=chromium.org; dkim=pass (1024-bit key) header.d=chromium.org header.i=@chromium.org header.b=ioA7tJAE; arc=none smtp.client-ip=209.85.214.176 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=chromium.org Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=chromium.org Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=chromium.org header.i=@chromium.org header.b="ioA7tJAE" Received: by mail-pl1-f176.google.com with SMTP id d9443c01a7336-214d1c6d724so2999465ad.3 for ; Wed, 27 Nov 2024 19:54:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; t=1732766046; x=1733370846; darn=vger.kernel.org; h=content-disposition:mime-version:message-id:subject:cc:to:from:date :from:to:cc:subject:date:message-id:reply-to; bh=TF5il+e7Kq8fof0AwUQ4lkAD7fimdwuQEUr9/oLqqYc=; b=ioA7tJAEMGkTKmaX/OlxNBWXupm9WeXYdyKObiWfLliaC2x129hzB78VRo7JhEju0d S3o8Z1WokV0S07+M5L4KkZFvB3XUu0S07yj/shomHQpHE0kkejCHTcmTXDp7vcSARCCl PdcpDIRPj3YDfJQ9cNVw5VkSi8fLlBOlhYGvA= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1732766046; x=1733370846; h=content-disposition:mime-version:message-id:subject:cc:to:from:date :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=TF5il+e7Kq8fof0AwUQ4lkAD7fimdwuQEUr9/oLqqYc=; b=MdZX5zUcicg41u154mtzUik9JNJCdMsPm0Ku7cj3GI8c3a/oTh4l03uEra6whtZ0Lx Njm82pOiP1i7jXOY0mpBqOnCUTEy2BhWiBai22EShMImRs7zc5U0gVIsxEb+zSfJ2tVe pRPSFtP6rSyOvs5YuusA0o0d57bzG8sjzmE2vIMzS7XJHnbVdnnCzx2c6J3Zkl6RLrgl d4b6E3KhLEGrQs06U7Zj8/8GY/Gq0+ljO02eSTDeQMA0zAjWPO7Bs+E8ZaRMMuDuBa2y +ICizHr0oJQ92TWzmFAEkQpO7naZY/tR/fqZ58a7TQqvO5Aa9tkKOUB1M/rK6UZQFt1u 9H5g== X-Forwarded-Encrypted: i=1; AJvYcCWYY4fTOVJ8jeTiel0UA/Rrk2ZneaU5jMWCDakAn5M4miKpZ5ZH+ihwMUm9Dl22iCn0Y2yTjDhQDTnSmBKg@vger.kernel.org X-Gm-Message-State: AOJu0YwjfmTe6WRocx8gviVS/o4Gg41cA89FXBLovhWZ6K4D0dQ4mTa4 /+4aF0LZs2ySNDv9NoAOG/4pcdwdHdqF1f4/lSJguVHA+/1Mh+haekgV7R6S9A== X-Gm-Gg: ASbGnctuKUeytNqPCJjsOcyxK0zTD6BXQp7x5UrtsydZ+uV0mPkwoH6CNEgYmlhDkkc ah1FSA66IaeeCi/4vWSTylVkjDZhhVJj6AJnK5M7YXlMW3YghCfy5dfZn6K9Dsfw6nUYt9EVwWO Utim5g7EXvTy3vSbmbv2XFtk1uHbLJYr9I41+WUkBiI2gW3i/X2RzViViITKjIUVLFEPvBS6WAk s/2tHKJIgqbFFaRimAEhkM/LONjb3R9tB6Nw3AwlL3/Efo8t9esLg== X-Google-Smtp-Source: AGHT+IEnHytmJOdlEbxOpHUoUCVq72o0QdAQmffnOzCaX9vUp9WWUHEUK7ZrwamHbjp9SixH9iqliw== X-Received: by 2002:a17:902:d502:b0:212:6187:6a76 with SMTP id d9443c01a7336-215010960cfmr71640485ad.14.1732766045920; Wed, 27 Nov 2024 19:54:05 -0800 (PST) Received: from google.com ([2401:fa00:8f:203:4351:dff5:9f71:a969]) by smtp.gmail.com with ESMTPSA id d9443c01a7336-215218f22c2sm3512125ad.26.2024.11.27.19.54.04 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 27 Nov 2024 19:54:05 -0800 (PST) Date: Thu, 28 Nov 2024 12:54:01 +0900 From: Sergey Senozhatsky To: Miklos Szeredi Cc: Tomasz Figa , linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, Sergey Senozhatsky Subject: fuse: fuse semantics wrt stalled requests Message-ID: <20241128035401.GA10431@google.com> Precedence: bulk X-Mailing-List: linux-fsdevel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hello Miklos, A question: does fuse define any semantics for stalled requests handling? We are currently looking at a number of hung_task watchdog crashes with tasks waiting forever in d_wait_lookup() for dentries to lose PAR_LOOKUP state, and we suspect that those dentries are from fuse mount point (we also sometimes see hung_tasks in fuse_lookup()->fuse_simple_request()). Supposedly (a theory) some tasks are in request_wait_answer() under PAR_LOOKUP, and the rest of tasks are waiting for them to finish and clear PAR_LOOKUP bit. request_wait_answer() waits indefinitely, however, the interesting thing is that it uses wait_event_interruptible() (when we wait for !fc->no_interrupt request to be processed). What is the idea behind interruptible wait? Is this, may be, for stall requests handling? Does fuse expect user-space to watchdog or monitor its processes/threads that issue syscalls on fuse mount points and, e.g., SIGKILL stalled ones? To make things even more complex, in our particular case fuse mount point mounts a remote google driver, so it become a network fs in some sense, which adds a whole new dimension of possibilities for stalled/failed requests. How those are expected to be handled? Should fuse still wait indefinitely or would it make sense to add a timeout to request_wait_answer() and FR_INTERRUPTED timeout-ed requests?