linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ian Kent <raven@themaw.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Michael Tokarev <mjt@tls.msk.ru>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Thomas Meyer <thomas@m3y3r.de>,
	autofs@vger.kernel.org
Subject: Re: autofs: make the autofsv5 packet file descriptor use a packetized pipe
Date: Mon, 30 Apr 2012 13:57:58 +0800	[thread overview]
Message-ID: <1335765478.2281.13.camel@perseus.themaw.net> (raw)
In-Reply-To: <CA+55aFzEefQWk+0EB2+dcL8DZcn+B7=1HZ1MV0HVMX7prhrmVA@mail.gmail.com>

On Sun, 2012-04-29 at 18:56 -0700, Linus Torvalds wrote:
> On Sun, Apr 29, 2012 at 6:29 PM, Ian Kent <raven@themaw.net> wrote:
> >
> > autodir looks ok as well.
> >
> > http://sourceforge.net/projects/intraperson/files/latest/download
> 
> That looks odd, but safe.
> 
> Why does the code make the pipe file descriptor non-blocking, when it
> then always reads it using that odd "poll_read()" function that does a
> loop with poll() and read(). I guess there is some 1-second timeout
> thing.
> 
> It's a bit odd in other ways too. The "handle_events()" function is
> passed the fd, but then it never actually uses it, and uses
> 'autodir.k_pipe' instead.
> 
> So I'm having a bit of trouble following the *logic* to any of that,
> but the only reads I found did seem to match the "read whole packet"
> model, so it does look ok too.

I'm only aware that autodir uses the module and wasn't involved in the
development.

I didn't look closely at it at all, just enough to check for reads to
the kernel pipe, so I don't know either.

I'm not sure that autodir is still maintained so the only thing I'll do
is include a cc to the autodir mailing list in a any follow up mail to
the autofs list explaining the outcome of this work.

Ian



  reply	other threads:[~2012-04-30  5:58 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20120429205429.63CCD7C0064@ra.kernel.org>
2012-04-30  0:15 ` autofs: make the autofsv5 packet file descriptor use a packetized pipe H. Peter Anvin
2012-04-30  0:25   ` Linus Torvalds
2012-04-30  0:28     ` H. Peter Anvin
2012-04-30  0:33       ` Linus Torvalds
2012-04-30  0:35         ` H. Peter Anvin
2012-04-30  0:43           ` Linus Torvalds
2012-04-30  0:45             ` H. Peter Anvin
2012-04-30  1:29             ` Ian Kent
2012-04-30  1:56               ` Linus Torvalds
2012-04-30  5:57                 ` Ian Kent [this message]
2012-04-30  0:30     ` H. Peter Anvin
2012-04-30  0:37       ` Linus Torvalds
2012-04-30 20:03       ` H. Peter Anvin
2012-04-30 20:11         ` Linus Torvalds
2012-04-30 20:14           ` H. Peter Anvin
2012-04-30  6:27   ` Michael Tokarev
2012-04-30  6:43     ` Michael Tokarev
2012-04-30  6:48       ` H. Peter Anvin
2012-04-30  6:55       ` Ian Kent

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=1335765478.2281.13.camel@perseus.themaw.net \
    --to=raven@themaw.net \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=autofs@vger.kernel.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjt@tls.msk.ru \
    --cc=thomas@m3y3r.de \
    --cc=torvalds@linux-foundation.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: 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).