public inbox for stgt@vger.kernel.org
 help / color / mirror / Atom feed
From: Alex Feng <li.feng@oracle.com>
To: FUJITA Tomonori <tomof@acm.org>
Cc: stgt@vger.kernel.org, lifeng1519@gmail.com
Subject: Re: [PATCH] fix timerfd support
Date: Wed, 11 May 2016 15:37:44 +0800	[thread overview]
Message-ID: <5732E148.2030601@oracle.com> (raw)
In-Reply-To: <20160510.083528.1682271453232720677.tomof@acm.org>

Hi Tomonori ,

Thanks for your response.
Please see my response inline.

On 2016/5/10 7:35, FUJITA Tomonori wrote:
> On Tue,  3 May 2016 16:45:38 +0800
> Feng Li <li.feng@oracle.com> wrote:
>
>> From: vonnyfly <lifeng1519@gmail.com>
>>
>> There are some exceptions when checking features in Makefile.
>> In my debian, timerfd.h path is not '/usr/include/sys/timerfd.h'.
>>
>>   $ find /usr/include -name "timerfd.h" | head -n1
>>   /usr/include/x86_64-linux-gnu/sys/timerfd.h
>>
>> In my raspberrypi, the path is also not here.
>>
>> So, it will not enable timerfd, even though it supports actually.
>> When I enable it after fix.  I have seen error logs.
>> "Failed to write to pipe".
>>
>>  From the code, we could know in add_work, it calls work_timer_schedule_evt.
>> work_timer_schedule_evt will call write(timer_fd[1], ...), then it will print error log,
>> because timer_fd[1] == -1.
> Looks like with timerfd enabled, work_timer_schedule_evt() isn't
> called. add_work() is always called with the non-zero second
> argument. How you hit the above bug?
The easiest way to see this log is to replace 'add_work(&nop_work, 1);' 
to 'add_work(&nop_work, 0);'.
Like this:

--- a/usr/iscsi/iscsi_tcp.c
+++ b/usr/iscsi/iscsi_tcp.c
@@ -438,7 +438,7 @@ static int iscsi_tcp_init(void)

         nop_work.func = iscsi_tcp_nop_work_handler;
         nop_work.data = &nop_work;
-       add_work(&nop_work, 1);
+       add_work(&nop_work, 0);

tgtd: work_timer_schedule_evt(69) Failed to write to pipe, Bad file 
descriptor

>
>> When enable timerfd support, makefile check incorrectly.
>> work_timer_schedule_evt should check support of timerfd.
>>
>> Signed-off-by: vonnyfly <lifeng1519@gmail.com>
>> ---
>>   usr/Makefile | 2 +-
>>   usr/work.c   | 2 +-
>>   2 files changed, 2 insertions(+), 2 deletions(-)
> Applied, thanks.

      reply	other threads:[~2016-05-11  7:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-03  8:45 [PATCH] fix timerfd support Feng Li
2016-05-09 23:35 ` FUJITA Tomonori
2016-05-11  7:37   ` Alex Feng [this message]

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=5732E148.2030601@oracle.com \
    --to=li.feng@oracle.com \
    --cc=lifeng1519@gmail.com \
    --cc=stgt@vger.kernel.org \
    --cc=tomof@acm.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