From owner-freebsd-wireless@freebsd.org Sun Feb 28 09:43:48 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4B0A9AB747C for ; Sun, 28 Feb 2016 09:43:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 20F2014D1 for ; Sun, 28 Feb 2016 09:43:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u1S9hlc7076840 for ; Sun, 28 Feb 2016 09:43:48 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 197498] [net80211]: Setting ssid on running interface in adhoc mode causes panic Date: Sun, 28 Feb 2016 09:43:48 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: avos@freebsd.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Feb 2016 09:43:48 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D197498 Andriy Voskoboinyk changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Open |In Progress --- Comment #6 from Andriy Voskoboinyk --- Before https://reviews.freebsd.org/D5145, scanning and -> INIT (FEXT REINIT) -> state transition were two solid parts. How things were worked: 1) network.subr executes 'ifconfig up', INIT -> SCAN (w/ FEXT_REINIT flag) state transition happens; 2) INIT -> INIT, FEXT_REINIT dropped; 3) INIT -> SCAN, scanning starts (and cannot be interrupted, since newstate_cb() uses the same taskqueue) 4) network.subr executes hostapd / wpa_supplicant -> interface reinitialize= s. 5) SCAN -> SCAN (w/ FEXT_REINIT flag); the task was enqueued, but (!) will = not be executed untill scan ends; 6) scan ends (no networks were seen, so it decides to create another one); = SCAN -> RUN state transition is enqueued (FEXT_REINIT is still here, but nstate = will be changed to RUN). 7) newstate_cb() is executed, SCAN -> INIT state transition (everything is dropped via ieee80211_reset_bss() call). 8) and INIT -> RUN state transition is issued (with corresponding result). Note: FEXT_REINIT is not added in STA mode, so it's not affected by this bu= g. --=20 You are receiving this mail because: You are the assignee for the bug.=