From: Wanlong Gao <gaowanlong@cn.fujitsu.com>
To: Jan Stancek <jstancek@redhat.com>,
Xiaoguang Wang <wangxg.fnst@cn.fujitsu.com>
Cc: ltp-list@lists.sourceforge.net, Artem Savkov <asavkov@redhat.com>
Subject: Re: [LTP] [PATCH 2/2] syscalls/getcwd04.c: regression test for getcwd(2)
Date: Mon, 21 Jul 2014 17:09:47 +0800 [thread overview]
Message-ID: <53CCD8DB.7030703@cn.fujitsu.com> (raw)
In-Reply-To: <38788431.12648558.1405933467675.JavaMail.zimbra@redhat.com>
On 07/21/2014 05:04 PM, Jan Stancek wrote:
>
>
> ----- Original Message -----
>> > From: "Xiaoguang Wang" <wangxg.fnst@cn.fujitsu.com>
>> > To: ltp-list@lists.sourceforge.net
>> > Sent: Tuesday, 15 July, 2014 12:13:49 PM
>> > Subject: [LTP] [PATCH 2/2] syscalls/getcwd04.c: regression test for getcwd(2)
>> >
>> > Note: this test has already been in xfstests generic/028 test case,
>> > I just port it to LTP.
>> >
>> > Kernel commit '232d2d60aa5469bb097f55728f65146bd49c1d25' introduced a race
>> > condition that causes getcwd(2) to return "/" instead of correct path.
>> > 232d2d6 dcache: Translating dentry into pathname without
>> > taking rename_lock
>> >
>> > And these two kernel commits have fixed this bug:
>> > ede4cebce16f5643c61aedd6d88d9070a1d23a68
>> > prepend_path() needs to reinitialize dentry/vfsmount/mnt on restarts
>> > f6500801522c61782d4990fa1ad96154cb397cd4
>> > f650080 __dentry_path() fixes
>> >
>> > This test is to check whether this bug exists in the running kernel,
>> > or whether this bug has been fixed.
>> >
>> > Signed-off-by: Xiaoguang Wang <wangxg.fnst@cn.fujitsu.com>
> Hi,
>
> looks good to me.
>
>> > I have run this test case in RHEL7.0GA, Fedora19, v3.11-7758-g232d2d6 and 3.16.0-rc4+.
>> > RHEL7.0GA has this kernel bug, so this test case fails.
> I can confirm this, with note that I've seen it happen only on systems with 2+ CPUs.
If this note is truth, we should judge the nr_cpus in this case to make sure it always
gives the right result.
Thanks,
Wanlong Gao
------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2014-07-21 9:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-15 10:13 [LTP] [PATCH 1/2] lib: add SAFE_RENAME() Xiaoguang Wang
2014-07-15 10:13 ` [LTP] [PATCH 2/2] syscalls/getcwd04.c: regression test for getcwd(2) Xiaoguang Wang
2014-07-15 10:21 ` Xiaoguang Wang
2014-07-21 9:04 ` Jan Stancek
2014-07-21 9:09 ` Wanlong Gao [this message]
2014-07-21 9:23 ` Xiaoguang Wang
2014-07-27 8:42 ` Xiaoguang Wang
2014-07-27 9:00 ` [LTP] [PATCH v2 1/2] lib: add SAFE_RENAME() Xiaoguang Wang
2014-07-27 9:00 ` [LTP] [PATCH v2 2/2] syscalls/getcwd04.c: regression test for getcwd(2) Xiaoguang Wang
2014-08-01 1:51 ` [LTP] [PATCH v2 1/2] lib: add SAFE_RENAME() Wanlong Gao
2014-07-21 9:33 ` [LTP] [PATCH 2/2] syscalls/getcwd04.c: regression test for getcwd(2) Jan Stancek
2014-07-21 9:40 ` Wanlong Gao
2014-07-21 9:58 ` Jan Stancek
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=53CCD8DB.7030703@cn.fujitsu.com \
--to=gaowanlong@cn.fujitsu.com \
--cc=asavkov@redhat.com \
--cc=jstancek@redhat.com \
--cc=ltp-list@lists.sourceforge.net \
--cc=wangxg.fnst@cn.fujitsu.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