[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <54dc62a9-22f4-44a2-a1e6-b7e1b44f2d1a@flourine.local>
Date: Thu, 24 Apr 2025 13:32:49 +0200
From: Daniel Wagner <dwagner@...e.de>
To: Hannes Reinecke <hare@...e.de>
Cc: Daniel Wagner <wagi@...nel.org>,
James Smart <james.smart@...adcom.com>, Christoph Hellwig <hch@....de>, Sagi Grimberg <sagi@...mberg.me>,
Chaitanya Kulkarni <kch@...dia.com>, Keith Busch <kbusch@...nel.org>, linux-nvme@...ts.infradead.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v5 08/14] nvmet-fcloop: prevent double port deletion
On Thu, Apr 24, 2025 at 12:17:32PM +0200, Hannes Reinecke wrote:
> > struct fcloop_rport *rport = remoteport->private;
> > + bool delete_port = true;
> > unsigned long flags;
> > flush_work(&rport->ls_work);
> > spin_lock_irqsave(&fcloop_lock, flags);
> > + if (test_and_set_bit(PORT_DELETED, &rport->flags))
> > + delete_port = false;
> > rport->nport->rport = NULL;
> > spin_unlock_irqrestore(&fcloop_lock, flags);
> > + if (!delete_port)
> > + return;
> > +
>
> The double negation is hard to follow. Can't you
> rename it to 'put_port' or somesuch and invert the logic?
Yes, was also not really happy with it but didn't really come up with a
good name. Thanks!
Powered by blists - more mailing lists