linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Al Viro <viro@ZenIV.linux.org.uk>
To: Daeho Jeong <daeho.jeong@samsung.com>
Cc: Eric Dumazet <edumazet@google.com>,
	"mguzik@redhat.com" <mguzik@redhat.com>,
	"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: Re: [PATCH] fs: initialize resize_wait wait queue of init task
Date: Wed, 17 May 2017 02:47:19 +0100	[thread overview]
Message-ID: <20170517014719.GV390@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20170517002519epcms1p31ef6730545cfb4652beab890a047805a@epcms1p3>

On Wed, May 17, 2017 at 12:25:19AM +0000, Daeho Jeong wrote:
> > I am curious, what kind of kernel threads are using file table ?
> > Thanks.
> 
> I don't know all the cases of that.
> But, in the embedded world, a lot of device drivers or kernel daemons are
> opening the files to just watch and read,
> or to write some log data.

Sure, but WTF would they want file descriptors for that?  All primitives
use struct file * anyway, so...

  reply	other threads:[~2017-05-17  1:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20170516064030epcas1p238af57ce4223442c821948621897d780@epcas1p2.samsung.com>
2017-05-16  6:40 ` [PATCH] fs: initialize resize_wait wait queue of init task Daeho Jeong
2017-05-16 14:10   ` Eric Dumazet
     [not found]   ` <CGME20170516064030epcas1p238af57ce4223442c821948621897d780@epcms1p3>
2017-05-17  0:25     ` Daeho Jeong
2017-05-17  1:47       ` Al Viro [this message]
     [not found]       ` <CGME20170516064030epcas1p238af57ce4223442c821948621897d780@epcms1p8>
2017-05-17  1:52         ` Daeho Jeong

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=20170517014719.GV390@ZenIV.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=daeho.jeong@samsung.com \
    --cc=edumazet@google.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=mguzik@redhat.com \
    /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: link
Be 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).