From patchwork Mon Oct 5 11:02:25 2015 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Jeff Layton X-Patchwork-Id: 7326301 Return-Path: X-Original-To: patchwork-linux-fsdevel@patchwork.kernel.org Delivered-To: patchwork-parsemail@patchwork2.web.kernel.org Received: from mail.kernel.org (mail.kernel.org [198.145.29.136]) by patchwork2.web.kernel.org (Postfix) with ESMTP id 151D3BEEA4 for ; Mon, 5 Oct 2015 11:03:03 +0000 (UTC) Received: from mail.kernel.org (localhost [127.0.0.1]) by mail.kernel.org (Postfix) with ESMTP id DAD3D206EB for ; Mon, 5 Oct 2015 11:02:57 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id DB02A206F8 for ; Mon, 5 Oct 2015 11:02:56 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751479AbbJELCx (ORCPT ); Mon, 5 Oct 2015 07:02:53 -0400 Received: from mail-qk0-f169.google.com ([209.85.220.169]:34715 "EHLO mail-qk0-f169.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751265AbbJELCw (ORCPT ); Mon, 5 Oct 2015 07:02:52 -0400 Received: by qkbi190 with SMTP id i190so46454965qkb.1 for ; Mon, 05 Oct 2015 04:02:51 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references; bh=EQ16Hh+rD/nw3ptqNtzrkERuqK+qkbe/Wjco/IKw5f4=; b=gcyQpW1CifpiuNijFDSo+33Yo8jQxV+YPCt5UiPVtl75EMgspZdIoOm5D+xzJDk6Zj oXyOmPCKA8zLJBUvf19D0f/Qp93CwkotbGnu90AeGLBvdTrl/Xf6Wz2I08X7HDkZRj8n j8yoyYZDZZqwbJL0GnnVtpEBvcWMLuVNpNL/Q/RBuRsWUZ2hYZi7iIkA6uwMcbWe6PKT RU1NGTtejI2B9wwEBzesrlpDSbfpN8xxnmGCI6b4cUkzO5WMx4LZNio9ke9ibFLlCqxC bfeHKMKwo/5EPyMjM+g2bETf6a4V7xTE1/JrqesM4+odQ2kiT7clt8QeUaqqm2L7g1jg 2y4Q== X-Gm-Message-State: ALoCoQmTxO7qQSCKJfNjGB7C7fqYKO/8EwS6/uR6VXdwAKx3SeKk6DtVpBs9ADVxoUfn1TGxrDzf X-Received: by 10.55.198.212 with SMTP id s81mr4052610qkl.108.1444042971611; Mon, 05 Oct 2015 04:02:51 -0700 (PDT) Received: from tlielax.poochiereds.net ([2606:a000:1125:6079::d5a]) by smtp.googlemail.com with ESMTPSA id p39sm4977719qkp.47.2015.10.05.04.02.50 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 05 Oct 2015 04:02:51 -0700 (PDT) From: Jeff Layton X-Google-Original-From: Jeff Layton To: bfields@fieldses.org Cc: linux-nfs@vger.kernel.org, linux-fsdevel@vger.kernel.org, Al Viro Subject: [PATCH v5 03/20] fs: add a kerneldoc header to fput Date: Mon, 5 Oct 2015 07:02:25 -0400 Message-Id: <1444042962-6947-4-git-send-email-jeff.layton@primarydata.com> X-Mailer: git-send-email 2.4.3 In-Reply-To: <1444042962-6947-1-git-send-email-jeff.layton@primarydata.com> References: <1444042962-6947-1-git-send-email-jeff.layton@primarydata.com> Sender: linux-fsdevel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-fsdevel@vger.kernel.org X-Spam-Status: No, score=-6.9 required=5.0 tests=BAYES_00, RCVD_IN_DNSWL_HI, T_RP_MATCHES_RCVD, UNPARSEABLE_RELAY autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on mail.kernel.org X-Virus-Scanned: ClamAV using ClamSMTP ...and move its EXPORT_SYMBOL just below the function. Signed-off-by: Jeff Layton --- fs/file_table.c | 21 ++++++++++++++++++++- 1 file changed, 20 insertions(+), 1 deletion(-) diff --git a/fs/file_table.c b/fs/file_table.c index 52cc6803c07a..8cfeaee6323f 100644 --- a/fs/file_table.c +++ b/fs/file_table.c @@ -261,6 +261,25 @@ void flush_delayed_fput(void) flush_delayed_work(&delayed_fput_work); } +/** + * fput - put a struct file reference + * @file: file of which to put the reference + * + * This function decrements the reference count for the struct file reference, + * and queues it up for destruction if the count goes to zero. In the case of + * most tasks we queue it to the task_work infrastructure, which will be run + * just before the task returns back to userspace. kthreads however never + * return to userspace, so for those we add them to a global list and schedule + * a delayed workqueue job to do the final cleanup work. + * + * Why not just do it synchronously? __fput can involve taking locks of all + * sorts, and doing it synchronously means that the callers must take extra care + * not to deadlock. That can be very difficult to ensure, so by deferring it + * until just before return to userland or to the workqueue, we sidestep that + * nastiness. Also, __fput can be quite stack intensive, so doing a final fput + * has the possibility of blowing up if we don't take steps to ensure that we + * have enough stack space to make it work. + */ void fput(struct file *file) { if (atomic_long_dec_and_test(&file->f_count)) { @@ -281,6 +300,7 @@ void fput(struct file *file) schedule_delayed_work(&delayed_fput_work, 1); } } +EXPORT_SYMBOL(fput); /* * synchronous analog of fput(); for kernel threads that might be needed @@ -299,7 +319,6 @@ void __fput_sync(struct file *file) } } -EXPORT_SYMBOL(fput); void put_filp(struct file *file) {