[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6eeec2b6-ef28-4280-a854-cc22d2df55ed@web.de>
Date: Wed, 15 Oct 2025 18:25:00 +0200
From: Markus Elfring <Markus.Elfring@....de>
To: Shuhao Fu <sfual@....ust.hk>, linux-cifs@...r.kernel.org,
samba-technical@...ts.samba.org
Cc: Bharath SM <bharathsm@...rosoft.com>, Paulo Alcantara <pc@...guebit.org>,
Ronnie Sahlberg <ronniesahlberg@...il.com>,
Shyam Prasad N <sprasad@...rosoft.com>, Steve French <sfrench@...ba.org>,
Steve French <smfrench@...il.com>, Tom Talpey <tom@...pey.com>,
LKML <linux-kernel@...r.kernel.org>, kernel-janitors@...r.kernel.org
Subject: Re: [PATCH] smb: Fix refcount leak for cifs_sb_tlink
> Fix three refcount inconsistency issues related to `cifs_sb_tlink`.
I suggest to omit this introduction.
> Comments for `cifs_sb_tlink` state that `cifs_put_tlink()` needs to be
()?
> called after successful calls to `cifs_sb_tlink`. Three callsites fail
call sites?
> to update refcount accordingly, leading to possible resource leaks.
* Do we prefer the term “reference count”?
* Is the word “possible” really relevant here?
(Would you find corresponding case distinctions more helpful?)
* How do you think about to increase the application of scope-based resource management?
Regards,
Markus
Powered by blists - more mailing lists