[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20170829.104945.1786969849973428586.davem@davemloft.net>
Date: Tue, 29 Aug 2017 10:49:45 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: gregkh@...uxfoundation.org
Cc: devel@...verdev.osuosl.org, netdev@...r.kernel.org,
samuel@...tiz.org, linux-kernel@...r.kernel.org,
fengguang.wu@...el.com, geert@...ux-m68k.org
Subject: Re: [PATCH v2 net-next] irda: fix link order if IRDA is built into
the kernel
From: Greg KH <gregkh@...uxfoundation.org>
Date: Tue, 29 Aug 2017 19:46:22 +0200
> When moving the IRDA code out of net/ into drivers/staging/irda/net, the
> link order changes when IRDA is built into the kernel. That causes a
> kernel crash at boot time as netfilter isn't initialized yet.
>
> To fix this, build and link the irda networking code in the same exact
> order that it was previously before the move.
>
> Reported-by: kernel test robot <fengguang.wu@...el.com>
> Reported-by: Geert Uytterhoeven <geert@...ux-m68k.org>
> Signed-off-by: Greg Kroah-Hartman gregkh@...uxfoundation.org
Greg, just change the initializer in IRDA so that it will run
after subsys_init() when built statically.
IRDA is definitely not the first pontentially statically built
thing that needs netlink up and available.
Powered by blists - more mailing lists