linux-kernel - Re: Convert namespace

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <a781481a0705162200o744e16di5a1b8b6e41826d9d@mail.gmail.com>
Date:	Thu, 17 May 2007 10:30:29 +0530
From:	"Satyam Sharma" <satyam.sharma@...il.com>
To:	bharata@...ux.vnet.ibm.com
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Convert namespace_sem to a mutex

On 5/17/07, Bharata B Rao <bharata@...ux.vnet.ibm.com> wrote:
> From: Bharata B Rao <bharata@...ux.vnet.ibm.com>
>
> namespace_sem is a rwsem. It is acquired as read sem at only one place(used
                                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Actually, this ...

> by /proc/mounts, /proc/<pid>/mounts and /proc/<pid>/mountstats). In all other
> cases it is acquired as a write sem. So, as there is not more than one reader
                                              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

... does not mean this. Multiple threads could be reading mounts or
mountstats, and otoh mount(2) and umount(2) (acquire it as write sem)
could be less frequent?

> for this sem, this can be a generic sem (and not rwsem) and if so it can be
> a mutex.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/