public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: chrubis@suse.cz
To: Wanlong Gao <gaowanlong@cn.fujitsu.com>
Cc: Garrett Cooper <yanegomi@gmail.com>,
	LTP <ltp-list@lists.sourceforge.net>,
	Mike Frysinger <vapier@gentoo.org>
Subject: Re: [LTP] [PATCH 1/3] pthread_rwlock_rdlock:2-1: do not test on glibc
Date: Wed, 13 Nov 2013 16:13:23 +0100	[thread overview]
Message-ID: <20131113151322.GA12936@rei> (raw)
In-Reply-To: <52836390.5080104@cn.fujitsu.com>

Hi!
> > Since there was recently a discussion about this on glibc ML and some
> > clarfication requests for Austin Group were created, I would wait a
> > little more until the POSIX is clear on how this locks should behave and
> > then we can fix the tests (and possibly skip them on glibc).
> > 
> > See:
> > 
> > http://austingroupbugs.net/view.php?id=722
> > http://austingroupbugs.net/view.php?id=720
> 
> 
> Hi Cyril,
> 
> How about the discuss status? It's a POSIX SPEC bug? Do we need to fix our test suite?

I haven't been following the discussion for a while, I've read the
resolutions now.

So they removed the contradicting line from pthread_rwlock_wrlock() and
clarified the deadlock conditions.

If I understand the changes right, the write locks can now be
implemented to take precedence before the read locks, the testcase is
correct (actually three testcases pthread_rwlock_unlock_3-1,
pthread_rwlock_rdlock_2-1 and pthread_rwlock_rdlock_2-2) and the ball is
on glibc side. I will write a mail to the glibc ML to discuss it.

-- 
Cyril Hrubis
chrubis@suse.cz

------------------------------------------------------------------------------
DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps
OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access
Free app hosting. Or install the open source package on any LAMP server.
Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native!
http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

  parent reply	other threads:[~2013-11-13 15:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1374807380-20319-1-git-send-email-gaowanlong@cn.fujitsu.com>
2013-07-26  7:07 ` [LTP] [PATCH 1/3] pthread_rwlock_rdlock:2-1: do not test on glibc Jan Stancek
2013-07-26  7:52   ` Wanlong Gao
2013-07-26  8:28     ` Jan Stancek
2013-07-26  8:30       ` Wanlong Gao
2013-07-31 11:16 ` chrubis
     [not found]   ` <52836390.5080104@cn.fujitsu.com>
2013-11-13 15:13     ` chrubis [this message]
     [not found]       ` <52D5F124.3090204@cn.fujitsu.com>
2014-01-28 13:23         ` chrubis

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=20131113151322.GA12936@rei \
    --to=chrubis@suse.cz \
    --cc=gaowanlong@cn.fujitsu.com \
    --cc=ltp-list@lists.sourceforge.net \
    --cc=vapier@gentoo.org \
    --cc=yanegomi@gmail.com \
    /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