netdev - Re: [PATCH] cnic: Give a chance for the uio device to be opened before failing the path request

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Fri, 09 Apr 2010 15:49:45 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	benli@...adcom.com
Cc:	netdev@...r.kernel.org, mchan@...adcom.com, waie@...adcom.com
Subject: Re: [PATCH] cnic: Give a chance for the uio device to be opened
 before failing the path request

From: "Benjamin Li" <benli@...adcom.com>
Date: Thu, 8 Apr 2010 14:34:28 -0700

> There is a timing condition; where the time between the CNIC's
> /dev/uio* device registration and then the issuing of path requests
> messages is faster the brcm_iscsiuio daemon initializing.
> 
> This can be seen if one sets the machine to automatically login into
> iSCSI targets.  Then reset the network and iscsi daemons in quick
> succession.  The login will fail because iscsid will only try
> a couple of times in quick succession.  This patch will allow some
> additional needed time for the brcm_iscsiuio daemon to initialize
> before failing the path request call.
> 
> Signed-off-by: Benjamin Li <benli@...adcom.com>
> Signed-off-by: Eddie Wai <waie@...adcom.com>

You need to create a proper serialization scheme to fix this.

Any delay value you choose is arbitrary, and could be easily exceeded
if swapping or other expensive operations are in propgress at the time
of the regristration.

Therefore all delay based schemes have a failure mode and therefore
isn't the way to fix this properly.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html