On 03/22/2017 10:15 AM, Stanislaw Gruszka wrote:
On Sat, Mar 18, 2017 at 04:30:04PM -0500, Larry Finger wrote:
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 <[email protected]>
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?
Due to conflicts, I cannot simply revert it; however if I check out
the previous commit 489111e5c25b93be80340c3113d71903d7c82136
("genetlink: statically initialize families"), then the kernel is
OK.
I just posted a patch which most likely fixes this problem. I have some
other issue on my setup, but seems this issue is also caused by the
same bug in 2ae0f17df1cd52aafd1ab0415ea1f1dd56dc0e2a.
Stanislaw,
Your patch does fix this problem. Thanks.
Larry
