From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=100.103.45.18 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1793631651; b=XTlyfzAMgHMT7tCZrYozWJLe8mAXfprkr0PIBD8J0m8vVB5Z3UQiDqzSuNODixa1O2Pb d20ACuEcyM2V5NvHMHJKIMMEr76xVFbL0A5BYuqUNcmrEFfG30DZTIYQBjMaErEAw1GhJ 9TR9jzO4J3peBpv8X3W5PvJbrKkciAmHQBM/hm6QUceMsaSgz8C9y/AabU65NRUdBrG5r DPa7KYY0O4bdNqqiqQgUgN/pQN9GEL46LUm6lxzxggLPbLjq4iaK5TkLI8T2Mvq/NY/bl 70PyBVknTx4yr82GVXgWOVztQ0hfMwe31potnFfI+ByAzvkWsBPHcbQ528gl6QDwpRQ== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1793631651; h=Received:DKIM-Signature:From:Date:Subject:MIME-Version:Content-Type: Content-Transfer-Encoding:Message-Id:References:In-Reply-To:To:Cc: X-Mailer; bh=WexYP4n/eJfrpqN/7Y/99TWN9UmEAiTX3zfhZnWQ9bk=; b=qHjCQR2x8NzSXwBWswKgP/3TAeU7rgCtFljNyF7kRpJt/ge2l0UWwRI6raan/jXYOn7W 1TCQTTMESQ3RDPjlG2dic1Uj4dClVcocuOmLZ8HY/oI/P3U9Ez4vUlKbjN6IXtnsLnA/i U4+Dfsm1mcd7k8YfpsTUApFbFE2Us8ka4rrDUOf9Y0/anTDptPaVrHcunOf8GR7P7ZEeg 9CPKCNZQBDNHUqv+OiMBioTU384k+LyTSiR7/6oRUq8WXdIqkJ7g4s5HuJnmsXXOcSUwj kngDLoKxBVMlGqw08kkxbVstzgtH6F02oXwy5o6VCRpPewTCgHquS7q6vRTio4+8H0g== ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dkim=pass header.d=kernel.org header.i=@kernel.org header.a=rsa-sha256 header.s=k20260515 header.b="A2/gsEkz"; arc=none smtp.remote-ip=100.103.45.18 Received: from smtp.kernel.org (quasi.space.kernel.org [100.103.45.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 2ED8660703B1; Mon, 2 Nov 2026 15:00:50 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key, unprotected) header.d=kernel.org header.i=@kernel.org header.a=rsa-sha256 header.s=k20260515 header.b=A2/gsEkz Received: by smtp.kernel.org (Postfix) with ESMTPSA id A46471F00A1B; Mon, 2 Nov 2026 15:00:34 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1793631650; bh=WexYP4n/eJfrpqN/7Y/99TWN9UmEAiTX3zfhZnWQ9bk=; h=From:Date:Subject:References:In-Reply-To:To:Cc; b=A2/gsEkzx2kBH18SAsxMbRE7DBXdXekO2k0AMONwA38NS2BeDGH6AlKZL03w4/28l 7qWi2rG2rJCWCR6+fbGSYz+CfWBV0Ci0pF1WeeGvh6x87o68IUijRVhLCAnsysE63g gFW4a3WlIujXOTwoCGxu2R7gkXBHQf9Y1YqE1Xn6xpgRz7WVUtfd1WZ2apgDKGSK05 CHRuIqGLl2EMG0sbV4xVnf0DD6i/OjIG8NGo5Z2uNU2Yncmc6lhQtFvkCw+w0QxB8K hyIvh2pJ26eus4ARKhd4/cgXcKyC0J9MQ7UMZ1MRtXXvwcQWXKCar7BuOtiH+1SPZY WmQletXJipnOw== From: Christian Brauner Date: Mon, 02 Nov 2026 15:48:56 +0100 Subject: [PATCH RFC 16/16] Documentation: seq_file: describe how a /proc file uses seq_file X-Mailing-List: linux-input@vger.kernel.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <20261102-work-procfs-core-v1-16-75df35e4f8b8@kernel.org> References: <20261102-work-procfs-core-v1-0-75df35e4f8b8@kernel.org> In-Reply-To: <20261102-work-procfs-core-v1-0-75df35e4f8b8@kernel.org> To: linux-fsdevel@vger.kernel.org Cc: Linus Torvalds , Jann Horn , Josef Bacik , Chris Mason , Jeff Layton , NeilBrown , Eric Dumazet , Thomas Gleixner , Al Viro , Jonathan Corbet , Christoph Hellwig , Greg Kroah-Hartman , Joel Granados , Kees Cook , Jan Kara , Jan Kara , linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org, linux-acpi@vger.kernel.org, linux-kselftest@vger.kernel.org, linux-s390@vger.kernel.org, linux-scsi@vger.kernel.org, linux-um@lists.infradead.org, linux-wireless@vger.kernel.org, linuxppc-dev@lists.ozlabs.org, netdev@vger.kernel.org, ntfs3@lists.linux.dev, platform-driver-x86@vger.kernel.org, coreteam@netfilter.org, kexec@lists.infradead.org, linux-pci@vger.kernel.org, linux-sound@vger.kernel.org, netfilter-devel@vger.kernel.org, dri-devel@lists.freedesktop.org, ibm-acpi-devel@lists.sourceforge.net, jfs-discussion@lists.sourceforge.net, linux-alpha@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-cifs@vger.kernel.org, linux-fbdev@vger.kernel.org, linux-hwmon@vger.kernel.org, linux-mm@kvack.org, linux-sh@vger.kernel.org, linux-usb@vger.kernel.org, samba-technical@lists.samba.org, sparclinux@vger.kernel.org, linux-m68k@lists.linux-m68k.org, linux-doc@vger.kernel.org, linux-serial@vger.kernel.org, linux-atm-general@lists.sourceforge.net, Takashi Iwai , linux-input@vger.kernel.org, linux-raid@vger.kernel.org, linux-ext4@vger.kernel.org, linux-modules@vger.kernel.org, linux-debuggers@vger.kernel.org, "Christian Brauner (Amutable)" , Chuck Lever X-Mailer: b4 0.17-dev The example in seq_file.rst hands proc_create() file operations built from an open method that calls seq_open() and from seq_read(), seq_lseek() and seq_release(). procfs doesn't work that way anymore. It opens and releases the seq_file itself when the entry declares its seq_operations or its show function in struct proc_ops. Say so, and point the extra-simple version at ->proc_show() for /proc files. Signed-off-by: Christian Brauner (Amutable) --- Documentation/filesystems/seq_file.rst | 42 ++++++++++++++++++++++++++-------- 1 file changed, 33 insertions(+), 9 deletions(-) diff --git a/Documentation/filesystems/seq_file.rst b/Documentation/filesystems/seq_file.rst index d753d8177bcb..8cfb5fdabe99 100644 --- a/Documentation/filesystems/seq_file.rst +++ b/Documentation/filesystems/seq_file.rst @@ -68,7 +68,7 @@ kernel 3.10. Current versions require the following update:: - entry = create_proc_entry("sequence", 0, NULL); - if (entry) - entry->proc_fops = &ct_file_ops; - + entry = proc_create("sequence", 0, NULL, &ct_file_ops); + + entry = proc_create("sequence", 0, NULL, &ct_proc_ops); The iterator interface ====================== @@ -277,9 +277,10 @@ seq_file system, but we have not yet turned them into a file that a user can see. Creating a file within the kernel requires, of course, the creation of a set of file_operations which implement the operations on that file. The seq_file interface provides a set of canned operations which do -most of the work. The virtual file author still must implement the open() -method, however, to hook everything up. The open function is often a single -line, as in the example module:: +most of the work. A file in /proc is special, procfs hooks the seq_file up +itself, see below. Everywhere else the virtual file author still must +implement the open() method to do that. The open function is often a +single line:: static int ct_open(struct inode *inode, struct file *file) { @@ -343,19 +344,38 @@ file_operations structure will look like:: There is also a seq_release_private() which passes the contents of the seq_file private field to kfree() before releasing the structure. -The final step is the creation of the /proc file itself. In the example -code, that is done in the initialization code in the usual way:: +The final step is the creation of the file itself. A file in /proc is +special here: procfs opens and releases the seq_file itself, so there is +no open method and no file_operations for it. The entry declares its +seq_operations in struct proc_ops instead, and the size of a private +block in proc_state_size if it wants procfs to allocate one like +seq_open_private() would:: + + static const struct proc_ops ct_proc_ops = { + .proc_seq_ops = &ct_seq_ops, + }; static int ct_init(void) { - struct proc_dir_entry *entry; - - proc_create("sequence", 0, NULL, &ct_file_ops); + proc_create("sequence", 0, NULL, &ct_proc_ops); return 0; } module_init(ct_init); +A ->proc_open() method of such an entry finds the seq_file in +file->private_data and may set up more state; ->proc_release() releases +only that. It runs when the entry is removed, which can be while a reader +is still copying out of the seq_file, so it must leave the seq_file +alone. procfs only calls into the entry between start() and stop() with +the entry pinned, so nothing that runs there may wait for something a +reader can hold while it copies to userspace, like the seq_file's lock. +start() and next() may return ERR_PTR(-EIO) to say that the entry is +gone; procfs unpins it right away then. An entry that wants to start out +with a larger buffer, like single_open_size() gives, calls +seq_preallocate() from ->proc_open(). The file_operations above are what +a file elsewhere, in debugfs for example, uses. + And that is pretty much it. @@ -394,3 +414,7 @@ value given to single_open() can be found in the private field of the seq_file structure. When using single_open(), the programmer should use single_release() instead of seq_release() in the file_operations structure to avoid a memory leak. + +A file in /proc puts the show() function into the proc_show field of its +struct proc_ops instead and procfs does the rest, with the entry's data in +the private field of the seq_file structure. -- 2.53.0