All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fengguang Wu <fengguang.wu@intel.com>
To: Davidlohr Bueso <davidlohr@hp.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	LKML <linux-kernel@vger.kernel.org>
Subject: [ipc] 5769cf63: LTP semget02 TFAILs
Date: Fri, 17 Jan 2014 18:24:28 +0800	[thread overview]
Message-ID: <20140117102428.GC8751@localhost> (raw)

Hi Davidlohr,

We noticed LTP test failures

        ltp.msgget02.1.TFAIL
        ltp.semget02.2.TFAIL
        ltp.semget02.3.TFAIL

and the first bad commit is

commit 5769cf6355d87f63906b3e51887eff7017c39217
Author:     Davidlohr Bueso <davidlohr@hp.com>
AuthorDate: Wed Jan 15 16:56:01 2014 +1100
Commit:     Stephen Rothwell <sfr@canb.auug.org.au>
CommitDate: Wed Jan 15 16:56:01 2014 +1100

    ipc: share ids rwsem when possible in ipcget_public
    
    ...  and rewrite the function.  For scenarios where the key is found and
    we end up just doing different routinary checks, we can downgrade the
    ids->rwsem and share it among concurrent readers.  These checks include
    the following, which are all safe to share the lock:
    
    ops->more_checks() >>  sem_more_checks(), shm_more_checks()
    ipc_check_perms()  >>  ipcperms(),ops->associate() >> [lsm]_[ipctype]_associate()
    
    Signed-off-by: Davidlohr Bueso <davidlohr@hp.com>
    Cc: Aswin Chandramouleeswaran <aswin@hp.com>
    Cc: Rik van Riel <riel@redhat.com>
    Cc: Manfred Spraul <manfred@colorfullife.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>

 ipc/util.c | 60 +++++++++++++++++++++++++++++++++---------------------------
 1 file changed, 33 insertions(+), 27 deletions(-)

Thanks,
Fengguang

             reply	other threads:[~2014-01-17 10:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-17 10:24 Fengguang Wu [this message]
2014-01-17 13:08 ` [ipc] 5769cf63: LTP semget02 TFAILs Stephen Rothwell
2014-01-17 21:24 ` Andrew Morton

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=20140117102428.GC8751@localhost \
    --to=fengguang.wu@intel.com \
    --cc=davidlohr@hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.