On Wed, Jun 05, 2024 at 12:44:56PM +0300, Leon Romanovsky wrote: > On Tue, Jun 04, 2024 at 01:36:36PM -0300, Jason Gunthorpe wrote: > > On Tue, May 28, 2024 at 03:52:51PM +0300, Leon Romanovsky wrote: > > > From: Leon Romanovsky <leonro@xxxxxxxxxx> > > > > > > When the table is released, we nullify pointer to GID table, it means > > > that in case GID entry leak is detected, we will leak table too. > > > > > > Delete code that prevents table destruction. > > > > This converts a memory leak into a UAF, it doesn't seem like a good direction?? > > Maybe we should convert dev_err() to be WARN_ON(). I didn't see any > complains about GID entry leaks. It is debug print. Yes WARN_ON is better Jason
