From: Wanlong Gao <gaowanlong@cn.fujitsu.com>
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: Wed, 28 Aug 2013 13:20:25 +0800 [thread overview]
Message-ID: <521D8899.3000307@cn.fujitsu.com> (raw)
In-Reply-To: <2060663a46bc8d66f90a9686c7fe4a83d21e40a4.1377594171.git.jstancek@redhat.com>
On 08/27/2013 05:05 PM, Jan Stancek wrote:
> 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>
Pushed
Wanlong Gao
------------------------------------------------------------------------------
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
prev parent reply other threads:[~2013-08-28 5:21 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
2013-08-28 5:20 ` Wanlong Gao [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=521D8899.3000307@cn.fujitsu.com \
--to=gaowanlong@cn.fujitsu.com \
--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