From: Sedat Dilek <sedat.dilek@gmail.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: linux-mm <linux-mm@kvack.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] lockdep, rwsem: provide down_write_nest_lock()
Date: Sat, 5 Jan 2013 13:03:11 +0100 [thread overview]
Message-ID: <CA+icZUXZ3C6WvKcJKMzcW7Mbmoj4x49UvT0qGr3TeVHgA5AD+Q@mail.gmail.com> (raw)
In-Reply-To: <CA+icZUW_GdRdybS+-GJNXhzuyuzE3xdWC3AFZyD6pKS_JMKQ6A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1642 bytes --]
On Sat, Jan 5, 2013 at 12:08 PM, Sedat Dilek <sedat.dilek@gmail.com> wrote:
> Hi Jiri,
>
> I have tested your both patches (see [1] and [2])...
>
> Patch #1: [PATCH 1/2] lockdep, rwsem: provide down_write_nest_lock()
> Patch #2: [PATCH 2/2] mm: mmap: annotate vm_lock_anon_vma locking
> properly for lockdep
>
> ...with "mmap10" testcase-script from Linux Test Project (LTP version
> 20120903) [3].
>
> The mmap10-line I have seen in [4] and the result is attached.
>
> $ cd /opt/ltp/testcases/bin/
>
> $ sudo ./mmap10 -a -s -c 200 2>&1 | tee /tmp/mmap10-a-s-c-200.txt
>
> I can't say if this satisfy you. If you have any other testcases,
> please let me know.
>
> Feel free to add for both patches:
>
> Tested-by: Sedat Dilek <sedat.dilek@gmail.com>
>
> Regards,
> - Sedat -
>
> [1] http://marc.info/?l=linux-kernel&m=135734611921611&w=2
> [2] http://marc.info/?l=linux-kernel&m=135734616121633&w=2
> [3] http://sourceforge.net/projects/ltp/files/LTP%20Source/
> [4] http://marc.info/?l=linux-mm&m=135641033503993&w=2
>
> P.S.: Just as a note this warning seen with the mmap10-line (see above):
>
> [ QUOTE ]
> WARNING * WARNING * WARNING * WARNING * WARNING * WARNING * WARNING * WARNING
>
> The -c option is broken by desing. See:
>
> http://www.mail-archive.com/ltp-list@lists.sourceforge.net/msg13418.html
>
> In short don't use it in runtest files as the option will be removed.
>
> WARNING * WARNING * WARNING * WARNING * WARNING * WARNING * WARNING * WARNING
> [ /QUOTE ]
Attached are the results of runltplite.sh script:
$ cd /opt/ltp/
$ sudo LANG=C LC_ALL=C ./runltplite.sh 2>&1 | tee /tmp/runltplite-results.txt
- Sedat -
[-- Attachment #2: runltplite-results.txt.gz --]
[-- Type: application/x-gzip, Size: 44365 bytes --]
[-- Attachment #3: runltplite-results.txt.gz.sha256sum --]
[-- Type: application/octet-stream, Size: 92 bytes --]
99c691ce563a56e7cf1b02102f04281be517e7df5206f2902010b618b66a501a runltplite-results.txt.gz
next prev parent reply other threads:[~2013-01-05 12:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-05 11:08 Sedat Dilek
2013-01-05 12:03 ` Sedat Dilek [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-01-04 12:49 3.8-rc2: lockdep is complaining about mm_take_all_locks() Jiri Kosina
2013-01-05 0:34 ` [PATCH 1/2] lockdep, rwsem: provide down_write_nest_lock() Jiri Kosina
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=CA+icZUXZ3C6WvKcJKMzcW7Mbmoj4x49UvT0qGr3TeVHgA5AD+Q@mail.gmail.com \
--to=sedat.dilek@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/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