Re: [PATCH] mmap_lock: Change trace and locking order

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Liam Howlett <liam.howlett@xxxxxxxxxx>
Subject: Re: [PATCH] mmap_lock: Change trace and locking order
From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
Date: Fri, 3 Sep 2021 02:42:36 +0100
Cc: "linux-mm@xxxxxxxxx" <linux-mm@xxxxxxxxx>, "linux-kernel@xxxxxxxxxxxxxxx" <linux-kernel@xxxxxxxxxxxxxxx>, Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>, Steven Rostedt <rostedt@xxxxxxxxxxx>, Michel Lespinasse <walken.cr@xxxxxxxxx>, Vlastimil Babka <vbabka@xxxxxxx>
In-reply-to: <20210903013521.1802774-1-Liam.Howlett@oracle.com>
References: <20210903013521.1802774-1-Liam.Howlett@oracle.com>

On Fri, Sep 03, 2021 at 01:35:31AM +0000, Liam Howlett wrote:
> Print to the trace log before releasing the lock to avoid racing with
> other trace log printers of the same lock type.

Aren't you missing mmap_read_unlock_non_owner()?

Follow-Ups:
- Re: [PATCH] mmap_lock: Change trace and locking order
  - From: Liam Howlett

References:
- [PATCH] mmap_lock: Change trace and locking order
  - From: Liam Howlett

Prev by Date: Re: [PATCH v2 4/5] mm: Add zap_skip_check_mapping() helper
Next by Date: Re: [PATCH v2 4/5] mm: Add zap_skip_check_mapping() helper
Previous by thread: [PATCH] mmap_lock: Change trace and locking order
Next by thread: Re: [PATCH] mmap_lock: Change trace and locking order
Index(es):
- Date
- Thread

[Index of Archives] [Linux ARM Kernel] [Linux ARM] [Linux Omap] [Fedora ARM] [IETF Annouce] [Bugtraq] [Linux OMAP] [Linux MIPS] [eCos] [Asterisk Internet PBX] [Linux API]

Powered by Linux