mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: Paul Menage <menage@google.com>
Cc: containers@lists.linux-foundation.org,
	Zefan Li <lizf.kernel@gmail.com>,
	linux-kernel@vger.kernel.org, Xiaotian Feng <dfeng@redhat.com>
Subject: Re: [PATCH] cgroup: fix reverse unlock sequence in cgroup_get_sb
Date: Tue, 21 Jul 2009 21:17:11 +0530	[thread overview]
Message-ID: <20090721154711.GZ24157@balbir.in.ibm.com> (raw)
In-Reply-To: <6599ad830907210834y30e7d57aj978898a300a447d0@mail.gmail.com>

* menage@google.com <menage@google.com> [2009-07-21 08:34:51]:

> On Tue, Jul 21, 2009 at 5:01 AM, Balbir Singh<balbir@linux.vnet.ibm.com> wrote:
> >
> > lock(A)
> > lock(B)
> > unlock(A)
> > unlock(B)
> >
> > Tomorrow if a unsuspecting programmer does this
> >
> > lock(A)
> > lock(B)
> > unlock(A)
> >
> > code block
> >
> > unlock(B)
> >
> >
> > What protects code block? lock B? Is that the intention?
> >
> 
> An "unsuspecting programmer" shouldn't be adding code to
> multi-threaded routines without thoroughly understanding the locking.
> 

Agreed, but why leave behind places for people to do so. There is the
consistency factor as well, see below.


> I guess there's no harm in this patch, but as Li says, it doesn't
> really change anything.
>

Well all the other places do it right in the same routine. 

-- 
	Balbir

  reply	other threads:[~2009-07-21 15:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-21 10:25 Xiaotian Feng
2009-07-21 11:10 ` Balbir Singh
2009-07-21 11:12   ` Danny Feng
     [not found]   ` <8522a3d30907210438u6fce081fi835bf964d0c01e8a@mail.gmail.com>
2009-07-21 12:01     ` Balbir Singh
2009-07-21 15:34       ` Paul Menage
2009-07-21 15:47         ` Balbir Singh [this message]
2009-07-22  0:53       ` Li Zefan
2009-07-22  1:42         ` Danny Feng
2009-07-21 16:03 ` Paul Menage
2009-07-22  1:57   ` Danny Feng
2009-07-22  2:18     ` Li Zefan
2009-07-22  2:32       ` Danny Feng

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=20090721154711.GZ24157@balbir.in.ibm.com \
    --to=balbir@linux.vnet.ibm.com \
    --cc=containers@lists.linux-foundation.org \
    --cc=dfeng@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizf.kernel@gmail.com \
    --cc=menage@google.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

all inboxes | Powered by JetHome®