Re: [PATCH RT] kmemleak: Change the lock of kmemleak_object to raw_spinlock_t

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

To: Yongxin Liu <yongxin.liu@xxxxxxxxxxxxx>
Subject: Re: [PATCH RT] kmemleak: Change the lock of kmemleak_object to raw_spinlock_t
From: Sebastian Andrzej Siewior <bigeasy@xxxxxxxxxxxxx>
Date: Mon, 7 Oct 2019 18:15:39 +0200
Cc: linux-kernel@xxxxxxxxxxxxxxx, linux-rt-users@xxxxxxxxxxxxxxx, tglx@xxxxxxxxxxxxx, rostedt@xxxxxxxxxxx, haitao.liu@xxxxxxxxxxxxx, zhe.he@xxxxxxxxxxxxx
In-reply-to: <20190927082230.34152-1-yongxin.liu@windriver.com>
References: <20190927082230.34152-1-yongxin.liu@windriver.com>
User-agent: NeoMutt/20180716

On 2019-09-27 16:22:30 [+0800], Yongxin Liu wrote:
> From: Liu Haitao <haitao.liu@xxxxxxxxxxxxx>
> 
> The following call trace would be triggered as kmemleak is running.
> 
…

Applied.

Sebastian

References:
- [PATCH RT] kmemleak: Change the lock of kmemleak_object to raw_spinlock_t
  - From: Yongxin Liu

Prev by Date: Re: [RFC PATCH] lib/ubsan: Don't seralize UBSAN report
Next by Date: Re: [PATCH] mm: vmalloc: Use the vmap_area_lock to protect ne_fit_preload_node
Previous by thread: [PATCH RT] kmemleak: Change the lock of kmemleak_object to raw_spinlock_t
Next by thread: [ANNOUNCE] v5.2.17-rt9
Index(es):
- Date
- Thread

[Index of Archives] [RT Stable] [Kernel Newbies] [IDE] [Security] [Git] [Netfilter] [Bugtraq] [Yosemite] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Linux ATA RAID] [Samba] [Video 4 Linux] [Device Mapper]

Powered by Linux