public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: chrubis@suse.cz
To: Jan Stancek <jstancek@redhat.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH] proc01: add use-gss-proxy to known_issues list
Date: Tue, 27 Aug 2013 13:47:33 +0200	[thread overview]
Message-ID: <20130827114733.GD10995@rei.Home> (raw)
In-Reply-To: <2060663a46bc8d66f90a9686c7fe4a83d21e40a4.1377594171.git.jstancek@redhat.com>

Hi!
> Following commit implemented non-blocking read for use-gss-proxy:
>   commit b161c144404c18f6a9e20e46b63828ae3c2eb093
>   Author: J. Bruce Fields <bfields@redhat.com>
>     Date:   Fri May 24 09:47:49 2013 -0400
>         svcrpc: implement O_NONBLOCK behavior for use-gss-proxy
> 
> Prior to this commit non-block read hanged, but it happened
> only in -rc kernels, which we can ignore.
> 
> Note, that this proc entry is available only when you load module
> auth_rpcgss.
> 
> Signed-off-by: Jan Stancek <jstancek@redhat.com>

Acked.

-- 
Cyril Hrubis
chrubis@suse.cz

------------------------------------------------------------------------------
Introducing Performance Central, a new site from SourceForge and 
AppDynamics. Performance Central is your source for news, insights, 
analysis and resources for efficient Application Performance Management. 
Visit us today!
http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

  reply	other threads:[~2013-08-27 11:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-27  9:05 [LTP] [PATCH] proc01: add use-gss-proxy to known_issues list Jan Stancek
2013-08-27 11:47 ` chrubis [this message]
2013-08-28  5:20 ` Wanlong Gao

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=20130827114733.GD10995@rei.Home \
    --to=chrubis@suse.cz \
    --cc=jstancek@redhat.com \
    --cc=ltp-list@lists.sourceforge.net \
    /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