linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Omar Sandoval <osandov@osandov.com>
To: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>
Cc: Alexey Dobriyan <adobriyan@gmail.com>,
	Eric Biederman <ebiederm@xmission.com>,
	James Morse <james.morse@arm.com>,
	Bhupesh Sharma <bhsharma@redhat.com>,
	kernel-team@fb.com
Subject: [PATCH v2 1/7] proc/kcore: don't grab lock for kclist_add()
Date: Thu, 12 Jul 2018 17:09:33 -0700	[thread overview]
Message-ID: <ddbe991f42b8d49e50645878ad8c1a8168db2e82.1531440458.git.osandov@fb.com> (raw)
In-Reply-To: <cover.1531440458.git.osandov@fb.com>

From: Omar Sandoval <osandov@fb.com>

kclist_add() is only called at init time, so there's no point in
grabbing any locks. We're also going to replace the rwlock with a rwsem,
which we don't want to try grabbing during early boot.

Signed-off-by: Omar Sandoval <osandov@fb.com>
---
 fs/proc/kcore.c | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/fs/proc/kcore.c b/fs/proc/kcore.c
index 66c373230e60..ddeeb3a5a015 100644
--- a/fs/proc/kcore.c
+++ b/fs/proc/kcore.c
@@ -62,6 +62,7 @@ static LIST_HEAD(kclist_head);
 static DEFINE_RWLOCK(kclist_lock);
 static int kcore_need_update = 1;
 
+/* This doesn't grab kclist_lock, so it should only be used at init time. */
 void
 kclist_add(struct kcore_list *new, void *addr, size_t size, int type)
 {
@@ -69,9 +70,7 @@ kclist_add(struct kcore_list *new, void *addr, size_t size, int type)
 	new->size = size;
 	new->type = type;
 
-	write_lock(&kclist_lock);
 	list_add_tail(&new->list, &kclist_head);
-	write_unlock(&kclist_lock);
 }
 
 static size_t get_kcore_size(int *nphdr, size_t *elf_buflen)
-- 
2.18.0


  reply	other threads:[~2018-07-13  0:10 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-13  0:09 [PATCH v2 0/7] /proc/kcore improvements Omar Sandoval
2018-07-13  0:09 ` Omar Sandoval [this message]
2018-07-18  2:35   ` [PATCH v2 1/7] proc/kcore: don't grab lock for kclist_add() Andrew Morton
2018-07-18  3:19     ` Omar Sandoval
2018-07-13  0:09 ` [PATCH v2 2/7] proc/kcore: replace kclist_lock rwlock with rwsem Omar Sandoval
2018-07-18  2:38   ` Andrew Morton
2018-07-18  3:24     ` Omar Sandoval
2018-07-18  3:27       ` Andrew Morton
2018-07-18  3:36         ` Omar Sandoval
2018-07-13  0:09 ` [PATCH v2 3/7] proc/kcore: fix memory hotplug vs multiple opens race Omar Sandoval
2018-07-13  0:09 ` [PATCH v2 4/7] proc/kcore: hold lock during read Omar Sandoval
2018-07-13  0:09 ` [PATCH v2 5/7] proc/kcore: clean up ELF header generation Omar Sandoval
2018-07-13  0:09 ` [PATCH v2 6/7] proc/kcore: optimize multiple page reads Omar Sandoval
2018-07-13  0:09 ` [PATCH v2 7/7] proc/kcore: add vmcoreinfo note to /proc/kcore Omar Sandoval
2018-07-18  2:44   ` Andrew Morton
2018-07-18  3:27     ` Omar Sandoval

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=ddbe991f42b8d49e50645878ad8c1a8168db2e82.1531440458.git.osandov@fb.com \
    --to=osandov@osandov.com \
    --cc=adobriyan@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=bhsharma@redhat.com \
    --cc=ebiederm@xmission.com \
    --cc=james.morse@arm.com \
    --cc=kernel-team@fb.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).