Larry Finger <Larry.Finger@xxxxxxxxxxxx> writes: > On 03/18/2017 02:45 PM, Johannes Berg wrote: >> On Sat, 2017-03-18 at 12:41 -0500, Larry Finger wrote: >>> >>> I have duplicated your bug and I have bisected it to >>> >>> commit 2ae0f17df1cd52aafd1ab0415ea1f1dd56dc0e2a >>> Author: Johannes Berg <johannes.berg@xxxxxxxxx> >>> Date: Mon Oct 24 14:40:04 2016 +0200 >>> >>> genetlink: use idr to track families >>> >>> This patch is quite extensive and I have no idea which part is >>> failing, thus all I can do is report this confirmation. >> >> I don't think that makes any sense - have you verified that reverting >> that makes it go away? > > Something is wrong with my wireless-testing-next tree. I just built > the mainline 4.11-rc3, and it does not have the problem. I'm now sure > that the bisection was wrong. > > I will need to refresh w-d-n and try again. Do you mean wireless-drivers-next or wireless-testing? If the latter, please note that you cannot really bisect anything on wireless-testing because it's rebased every time. wireless-drivers-next should be safe to use for bisection because I don't rebase that unless a major disaster happens, and IIRC that has not yet happened. (Well, in theory you can bisect wireless-testing but you have to be _really_ careful how to bisect and make sure that you follow the history correctly. Definitely not recommended.) -- Kalle Valo
