public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Jan Stancek <jstancek@redhat.com>
To: Kang Kai <Kai.Kang@windriver.com>
Cc: ltp-list@lists.sourceforge.net,
	Zhenfeng Zhao <Zhenfeng.Zhao@windriver.com>
Subject: Re: [LTP] [PATCH] pthread_detach/4-3: workaround for segment fault
Date: Wed, 22 Aug 2012 04:58:59 -0400 (EDT)	[thread overview]
Message-ID: <40249568.8900482.1345625939805.JavaMail.root@redhat.com> (raw)
In-Reply-To: <5034984B.3020905@windriver.com>



----- Original Message -----
> From: "Kang Kai" <Kai.Kang@windriver.com>
> To: "Jan Stancek" <jstancek@redhat.com>
> Cc: gaowanlong@cn.fujitsu.com, ltp-list@lists.sourceforge.net, "Zhenfeng Zhao" <Zhenfeng.Zhao@windriver.com>
> Sent: Wednesday, 22 August, 2012 10:28:59 AM
> Subject: Re: [LTP] [PATCH] pthread_detach/4-3: workaround for segment fault

> Hi Jan,
> 
> > Is the above output from mips or x86_64?
> > Are you running it as root user?
> 
> This was tested on x86_64 with unprivileged  user. I retest it with
> root
> and test passes.

Your unprivileged user is hitting some resource limit, I'd be interested
to see how many threads are actually running at the same time. 

> It passes on routerstation(mips) with your patch too.
> So it looks like a race condition issue about stack attribute between
> threads, right?

I think so. We can try different way of signalling when threaded() is done
and try it again with all scenarios.

Regards,
Jan

> 
> Thanks a lot.
> Kai
> 


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

  reply	other threads:[~2012-08-22  8:59 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-21 10:35 [LTP] [PATCH] pthread_detach/4-3: workaround for segment fault Jan Stancek
2012-08-22  2:29 ` Kang Kai
2012-08-22  7:06   ` Jan Stancek
2012-08-22  8:28     ` Kang Kai
2012-08-22  8:58       ` Jan Stancek [this message]
2012-08-22 14:20         ` Jan Stancek
2012-08-23  6:21           ` Kang Kai
2012-08-23  7:09             ` Jan Stancek
2012-08-23 11:07               ` Jan Stancek
2012-08-24  2:46                 ` Kang Kai
2012-08-28  8:37                   ` Jan Stancek
2012-08-29  8:57                     ` Kang Kai
2012-08-29  9:21                       ` Jan Stancek
  -- strict thread matches above, loose matches on Subject: below --
2012-08-14  9:00 Kang Kai
2012-08-18 22:58 ` Wanlong Gao
2012-08-20  1:39   ` Kang Kai
2012-08-20  2:01     ` Wanlong Gao
2012-08-20  2:21       ` Kang Kai
2012-08-21  1:31         ` Kang Kai
2012-08-21  1:35           ` Wanlong Gao
2012-08-21  9:24             ` Kang Kai
2012-08-21  9:24               ` Wanlong Gao
2012-08-21  9:45               ` Jan Stancek
2012-08-21  9:59                 ` Kang Kai

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=40249568.8900482.1345625939805.JavaMail.root@redhat.com \
    --to=jstancek@redhat.com \
    --cc=Kai.Kang@windriver.com \
    --cc=Zhenfeng.Zhao@windriver.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