Re: [PATCH v1] mm: zswap: Fix a potential memory leak in zswap_decompress().

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

To: "Sridhar, Kanchana P" <kanchana.p.sridhar@xxxxxxxxx>
Subject: Re: [PATCH v1] mm: zswap: Fix a potential memory leak in zswap_decompress().
From: Johannes Weiner <hannes@xxxxxxxxxxx>
Date: Thu, 14 Nov 2024 00:11:49 -0500
Cc: Nhat Pham <nphamcs@xxxxxxxxx>, Yosry Ahmed <yosryahmed@xxxxxxxxxx>, "linux-kernel@xxxxxxxxxxxxxxx" <linux-kernel@xxxxxxxxxxxxxxx>, "linux-mm@xxxxxxxxx" <linux-mm@xxxxxxxxx>, "chengming.zhou@xxxxxxxxx" <chengming.zhou@xxxxxxxxx>, "usamaarif642@xxxxxxxxx" <usamaarif642@xxxxxxxxx>, "ryan.roberts@xxxxxxx" <ryan.roberts@xxxxxxx>, "Huang, Ying" <ying.huang@xxxxxxxxx>, "21cnbao@xxxxxxxxx" <21cnbao@xxxxxxxxx>, "akpm@xxxxxxxxxxxxxxxxxxxx" <akpm@xxxxxxxxxxxxxxxxxxxx>, "Feghali, Wajdi K" <wajdi.k.feghali@xxxxxxxxx>, "Gopal, Vinodh" <vinodh.gopal@xxxxxxxxx>
In-reply-to: <SJ0PR11MB56785F052557B685054AF74AC95B2@SJ0PR11MB5678.namprd11.prod.outlook.com>
References: <20241113052413.157039-1-kanchana.p.sridhar@intel.com> <CAJD7tkZWDhOXyyZnEYFiS7F4tSV+z6TYXUYiEcrZrRuy_3R=ZA@mail.gmail.com> <DM8PR11MB567179534CEE154369CCA174C95A2@DM8PR11MB5671.namprd11.prod.outlook.com> <CAJD7tkbLtjQqR-uf8EBoFCWbkYOLHsVh6vJoMZUj+z4eN0GKAQ@mail.gmail.com> <SJ0PR11MB56781940E69ABE93FF9076F6C95A2@SJ0PR11MB5678.namprd11.prod.outlook.com> <20241113213007.GB1564047@cmpxchg.org> <SJ0PR11MB5678C24CDF6AA4FED306FC71C95A2@SJ0PR11MB5678.namprd11.prod.outlook.com> <CAKEwX=P6mxZ+-5UcunRHeoAVwtZD=UMfKqCGUeun-krJeT8ekg@mail.gmail.com> <SJ0PR11MB56785F052557B685054AF74AC95B2@SJ0PR11MB5678.namprd11.prod.outlook.com>

On Thu, Nov 14, 2024 at 01:56:16AM +0000, Sridhar, Kanchana P wrote:
> So my question was, can we prevent the migration to a different cpu
> by relinquishing the mutex lock after this conditional

Holding the mutex doesn't prevent preemption/migration.

Follow-Ups:
- RE: [PATCH v1] mm: zswap: Fix a potential memory leak in zswap_decompress().
  - From: Sridhar, Kanchana P

References:
- [PATCH v1] mm: zswap: Fix a potential memory leak in zswap_decompress().
  - From: Kanchana P Sridhar
- Re: [PATCH v1] mm: zswap: Fix a potential memory leak in zswap_decompress().
  - From: Yosry Ahmed
- RE: [PATCH v1] mm: zswap: Fix a potential memory leak in zswap_decompress().
  - From: Sridhar, Kanchana P
- Re: [PATCH v1] mm: zswap: Fix a potential memory leak in zswap_decompress().
  - From: Yosry Ahmed
- RE: [PATCH v1] mm: zswap: Fix a potential memory leak in zswap_decompress().
  - From: Sridhar, Kanchana P
- Re: [PATCH v1] mm: zswap: Fix a potential memory leak in zswap_decompress().
  - From: Johannes Weiner
- RE: [PATCH v1] mm: zswap: Fix a potential memory leak in zswap_decompress().
  - From: Sridhar, Kanchana P
- Re: [PATCH v1] mm: zswap: Fix a potential memory leak in zswap_decompress().
  - From: Nhat Pham
- RE: [PATCH v1] mm: zswap: Fix a potential memory leak in zswap_decompress().
  - From: Sridhar, Kanchana P

Prev by Date: Re: [PATCH] mm, doc: Update read_ahead_kb for MADV_HUGEPAGE
Next by Date: Re: [PATCH v4 1/1] memcg/hugetlb: Add hugeTLB counters to memcg
Previous by thread: RE: [PATCH v1] mm: zswap: Fix a potential memory leak in zswap_decompress().
Next by thread: RE: [PATCH v1] mm: zswap: Fix a potential memory leak in zswap_decompress().
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]