mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: jt@hpl.hp.com
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: Problem : can't make pipe non-blocking on 2.5.X
Date: Thu, 15 Aug 2002 06:46:18 +0900	[thread overview]
Message-ID: <87lm79ru51.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <20020814181902.GA24047@bougret.hpl.hp.com>

Jean Tourrilhes <jt@bougret.hpl.hp.com> writes:

> 	Hi,
> 
> 	I've got the following problem : I can't make a pipe
> non-blocking with 2.5.25.
> 	The various man pages don't mention anything
> about it (actually, the "fifo" man page say that non-blocking mode
> should succeed). And it seems to work fine on 2.4.20.
> 	Sorry if this has already been reported and fixed, but I
> quicly searched the changelog and archive and found nothing.
> 
> 	So, who should I complain to ?
> 

[...]

>   err = fcntl(trigger_pipe[0], F_GETFL, &flags);

F_GETFL should be,
    flags = fcntl(trigger_pipe[0], F_GETFL, 0);

>   fprintf(stderr, "GET FLAGS : %d - %X\n", err, flags);
>   if(err >= 0)
>     {
>       flags |= O_NONBLOCK;
>       err = fcntl(trigger_pipe[0], F_SETFL, flags);
>       fprintf(stderr, "SET FLAGS : %d - %d\n", err, errno);
>     }
>   return(0);
> }
> ------------- Output 2.5.25 ----------------
> GET FLAGS : 0 - 40045F18
> SET FLAGS : -1 - 22
> ------------- Output 2.4.20-pre2 -----------
> GET FLAGS : 0 - 40043F18
> SET FLAGS : 0 - 0
> --------------------------------------------

Looks like effect of different implement of O_DIRECT(0x40000).
Thanks.
-- 
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>

  parent reply	other threads:[~2002-08-14 21:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-14 18:19 Jean Tourrilhes
2002-08-14 18:43 ` Richard B. Johnson
2002-08-14 18:54   ` Jean Tourrilhes
2002-08-14 21:46 ` OGAWA Hirofumi [this message]
2002-08-14 21:52   ` Jean Tourrilhes

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=87lm79ru51.fsf@devron.myhome.or.jp \
    --to=hirofumi@mail.parknet.co.jp \
    --cc=jt@hpl.hp.com \
    --cc=linux-kernel@vger.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: 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

all inboxes | Powered by JetHome®