linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Christian Brauner <brauner@kernel.org>
To: Mateusz Guzik <mjguzik@gmail.com>
Cc: Christian Brauner <brauner@kernel.org>,
	akpm@linux-foundation.org, Liam.Howlett@oracle.com,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	ebiederm@xmission.com, oleg@redhat.com
Subject: Re: [PATCH v6 0/5] reduce tasklist_lock hold time on exit and do some pid cleanup
Date: Fri,  7 Feb 2025 10:18:22 +0100	[thread overview]
Message-ID: <20250207-wettkampf-binden-648f00063d8f@brauner> (raw)
In-Reply-To: <20250206164415.450051-1-mjguzik@gmail.com>

On Thu, 06 Feb 2025 17:44:09 +0100, Mateusz Guzik wrote:
> I fixed fat-fingering and touchedup some commit messages. git diff
> between the old and new branch does not show any code changes.
> 
> hopefully we will be done here after this iteration 8->
> 
> old cover letter:
> 
> [...]

This is great!

---

Applied to the kernel-6.15.tasklist_lock branch of the vfs/vfs.git tree.
Patches in the kernel-6.15.tasklist_lock branch should appear in linux-next soon.

Please report any outstanding bugs that were missed during review in a
new review to the original patch series allowing us to drop it.

It's encouraged to provide Acked-bys and Reviewed-bys even though the
patch has now been applied. If possible patch trailers will be updated.

Note that commit hashes shown below are subject to change due to rebase,
trailer updates or similar. If in doubt, please check the listed branch.

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: kernel-6.15.tasklist_lock

[1/5] exit: perform add_device_randomness() without tasklist_lock
      https://git.kernel.org/vfs/vfs/c/c8be3764feff
[2/5] exit: hoist get_pid() in release_task() outside of tasklist_lock
      https://git.kernel.org/vfs/vfs/c/9ee2997cbf14
[3/5] pid: sprinkle tasklist_lock asserts
      https://git.kernel.org/vfs/vfs/c/7d0030e1660c
[4/5] pid: perform free_pid() calls outside of tasklist_lock
      https://git.kernel.org/vfs/vfs/c/7b15589a575f
[5/5] pid: drop irq disablement around pidmap_lock
      https://git.kernel.org/vfs/vfs/c/07e518c464e8


  parent reply	other threads:[~2025-02-07  9:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-06 16:44 Mateusz Guzik
2025-02-06 16:44 ` [PATCH v6 1/5] exit: perform add_device_randomness() without tasklist_lock Mateusz Guzik
2025-02-06 16:44 ` [PATCH v6 2/5] exit: hoist get_pid() in release_task() outside of tasklist_lock Mateusz Guzik
2025-02-06 16:44 ` [PATCH v6 3/5] pid: sprinkle tasklist_lock asserts Mateusz Guzik
2025-02-06 16:44 ` [PATCH v6 4/5] pid: perform free_pid() calls outside of tasklist_lock Mateusz Guzik
2025-02-06 16:44 ` [PATCH v6 5/5] pid: drop irq disablement around pidmap_lock Mateusz Guzik
2025-02-06 17:14 ` [PATCH v6 0/5] reduce tasklist_lock hold time on exit and do some pid cleanup Liam R. Howlett
2025-02-07  9:18 ` Christian Brauner [this message]
2025-02-07  9:42   ` Oleg Nesterov

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=20250207-wettkampf-binden-648f00063d8f@brauner \
    --to=brauner@kernel.org \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mjguzik@gmail.com \
    --cc=oleg@redhat.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