mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andreas Gruenbacher <agruenba@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andreas Gruenbacher <agruenba@redhat.com>,
	cluster-devel@redhat.com, linux-kernel@vger.kernel.org
Subject: [GIT PULL] gfs2 debugfs improvements
Date: Sun,  9 Oct 2022 23:55:53 +0200	[thread overview]
Message-ID: <20221009215553.380150-1-agruenba@redhat.com> (raw)

Dear Linus,

please consider pulling the following gfs2 changes on top of the pull request
I've sent earlier today.

Commit "gfs2: Add glockfd debugfs file" modifies fs/file.c to export
task_lookup_next_fd_rcu(), and kernel/pid.c to export find_ge_pid().  We use
those two functions to iterate through all processes and their file
descriptors.  I haven't received any pushback to exporting those two functions,
but no affirmation, either.

The merge commit included in this pull request resolves a conflict in
gfs2_inode_lookup(); not sure if you'd rather like to squash this merge and
resolve the conflict directly; in any case, the merge commit shows the desired
end result.

Thank you very much,
Andreas

The following changes since commit 74b1b10e29b1f25e1a081fa82733baea65429d53:

  gfs2: Register fs after creating workqueues (2022-09-20 17:53:54 +0200)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2.git tags/gfs2-nopid-for-v6.1

for you to fetch changes up to c7d7d2d345697eb3781198e58a22504feb74af63:

  gfs2: Merge branch 'for-next.nopid' into for-next (2022-10-09 22:56:28 +0200)

----------------------------------------------------------------
gfs2 debugfs improvements

- Improve the way how the state of glocks is reported in debugfs
  for glocks which are not held by processes, but rather by other
  resouces like cached inodes or flocks.

----------------------------------------------------------------
Andreas Gruenbacher (6):
      gfs2: Add glockfd debugfs file
      gfs2: Add flocks to glockfd debugfs file
      gfs2: Add GL_NOPID flag for process-independent glock holders
      gfs2: Mark flock glock holders as GL_NOPID
      gfs2: Mark the remaining process-independent glock holders as GL_NOPID
      gfs2: Merge branch 'for-next.nopid' into for-next

 fs/file.c            |   1 +
 fs/gfs2/file.c       |  29 ++++++-
 fs/gfs2/glock.c      | 213 ++++++++++++++++++++++++++++++++++++++++++++++++---
 fs/gfs2/glock.h      |   1 +
 fs/gfs2/inode.c      |   5 +-
 fs/gfs2/ops_fstype.c |  14 ++--
 fs/gfs2/super.c      |   3 +-
 fs/gfs2/util.c       |   6 +-
 kernel/pid.c         |   1 +
 9 files changed, 248 insertions(+), 25 deletions(-)


             reply	other threads:[~2022-10-09 21:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-09 21:55 Andreas Gruenbacher [this message]
2022-10-11  3:43 ` pr-tracker-bot

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=20221009215553.380150-1-agruenba@redhat.com \
    --to=agruenba@redhat.com \
    --cc=cluster-devel@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®