LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Christian Brauner <christian@brauner.io> To: Florian Weimer <fweimer@redhat.com> Cc: viro@zeniv.linux.org.uk, linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-api@vger.kernel.org, jannh@google.com, oleg@redhat.com, tglx@linutronix.de, torvalds@linux-foundation.org, arnd@arndb.de, shuah@kernel.org, dhowells@redhat.com, tkjos@android.com, ldv@altlinux.org, miklos@szeredi.hu, linux-alpha@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-ia64@vger.kernel.org, linux-m68k@lists.linux-m68k.org, linux-mips@vger.kernel.org, linux-parisc@vger.kernel.org, linuxppc-dev@lists.ozlabs.org, linux-s390@vger.kernel.org, linux-sh@vger.kernel.org, sparclinux@vger.kernel.org, linux-xtensa@linux-xtensa.org, linux-arch@vger.kernel.org, linux-kselftest@vger.kernel.org, x86@kernel.org Subject: Re: [PATCH 1/2] open: add close_range() Date: Tue, 21 May 2019 15:23:23 +0200 [thread overview] Message-ID: <20190521132252.y5wt7d7o4bdjns4e@brauner.io> (raw) In-Reply-To: <87h89o9cng.fsf@oldenburg2.str.redhat.com> On Tue, May 21, 2019 at 03:10:11PM +0200, Florian Weimer wrote: > * Christian Brauner: > > >> Solaris has an fdwalk function: > >> > >> <https://docs.oracle.com/cd/E88353_01/html/E37843/closefrom-3c.html> > >> > >> So a different way to implement this would expose a nextfd system call > > > > Meh. If nextfd() then I would like it to be able to: > > - get the nextfd(fd) >= fd > > - get highest open fd e.g. nextfd(-1) > > The highest open descriptor isn't istering for fdwalk because nextfd > would just fail. Sure. I was thinking about other usecases. For example, sometimes in userspace you want to do the following: save_fd = dup(fd, <well-known-number-at-the-end-of-the-range); close_range(3, (save_fd - 1)); Which brings me to another point. So even if we don't do close_range() I would like libc to maybe give us something like close_range() for such scenarios. > > > But then I wonder if nextfd() needs to be a syscall and isn't just > > either: > > fcntl(fd, F_GET_NEXT)? > > or > > prctl(PR_GET_NEXT)? > > I think the fcntl route is a bit iffy because you might need it to get > the *first* valid descriptor. > > >> to userspace, so that we can use that to implement both fdwalk and > >> closefrom. But maybe fdwalk is just too obscure, given the existence of > >> /proc. > > > > Yeah we probably don't need fdwalk. > > Agreed. Just wanted to bring it up for completeness. I certainly don't > want to derail the implementation of close_range. > > Thanks, > Florian
next prev parent reply other threads:[~2019-05-21 13:23 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-05-21 11:34 [PATCH 1/2] open: add close_range() Christian Brauner 2019-05-21 11:34 ` [PATCH 2/2] tests: add close_range() tests Christian Brauner 2019-05-21 12:09 ` [PATCH 1/2] open: add close_range() Florian Weimer 2019-05-21 13:04 ` Christian Brauner 2019-05-21 13:10 ` Florian Weimer 2019-05-21 13:18 ` Christian Brauner 2019-05-21 13:23 ` Christian Brauner [this message] 2019-05-21 13:39 ` Rasmus Villemoes 2019-05-21 15:00 ` Al Viro 2019-05-21 16:53 ` Christian Brauner 2019-05-21 16:30 ` David Howells 2019-05-21 16:41 ` Christian Brauner 2019-05-21 20:23 ` Linus Torvalds 2019-05-22 8:12 ` Christian Brauner 2019-05-21 19:20 ` Al Viro 2019-05-21 19:59 ` Matthew Wilcox 2019-05-24 20:32 ` Michael Tirado
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20190521132252.y5wt7d7o4bdjns4e@brauner.io \ --to=christian@brauner.io \ --cc=arnd@arndb.de \ --cc=dhowells@redhat.com \ --cc=fweimer@redhat.com \ --cc=jannh@google.com \ --cc=ldv@altlinux.org \ --cc=linux-alpha@vger.kernel.org \ --cc=linux-api@vger.kernel.org \ --cc=linux-arch@vger.kernel.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-fsdevel@vger.kernel.org \ --cc=linux-ia64@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-kselftest@vger.kernel.org \ --cc=linux-m68k@lists.linux-m68k.org \ --cc=linux-mips@vger.kernel.org \ --cc=linux-parisc@vger.kernel.org \ --cc=linux-s390@vger.kernel.org \ --cc=linux-sh@vger.kernel.org \ --cc=linux-xtensa@linux-xtensa.org \ --cc=linuxppc-dev@lists.ozlabs.org \ --cc=miklos@szeredi.hu \ --cc=oleg@redhat.com \ --cc=shuah@kernel.org \ --cc=sparclinux@vger.kernel.org \ --cc=tglx@linutronix.de \ --cc=tkjos@android.com \ --cc=torvalds@linux-foundation.org \ --cc=viro@zeniv.linux.org.uk \ --cc=x86@kernel.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).