From: Greg KH <gregkh@linuxfoundation.org>
To: David Miller <davem@davemloft.net>
Cc: samuel@sortiz.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org
Subject: Re: [PATCH net-next] staging: irda: force to be a kernel module
Date: Tue, 29 Aug 2017 19:26:08 +0200 [thread overview]
Message-ID: <20170829172608.GA4700@kroah.com> (raw)
In-Reply-To: <20170829.093507.2166038228205751885.davem@davemloft.net>
On Tue, Aug 29, 2017 at 09:35:07AM -0700, David Miller wrote:
> From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Date: Tue, 29 Aug 2017 11:14:17 +0200
>
> > Now that the IRDA networking code has moved into drivers/staging/, the
> > link order is changed for when it is initialized if built into the
> > system. This can cause a crash when initializing as the netfilter core
> > hasn't been initialized yet.
> >
> > So force the IRDA code to be built as a module, preventing the crash.
> >
> > Reported-by: kernel test robot <fengguang.wu@intel.com>
> > Signed-off-by: Greg Kroah-Hartman gregkh@linuxfoundation.org
>
> I don't think this is reasonable.
>
> IRDA being built in was broken by moving it to staging, so it's a
> regression and we should find a way to fix it.
Hm, this is due to netlink coming before irda in the link order before
this patch series. I can't change the link order to put all of net/
before drivers/, which would solve this, and I don't think I can put:
obj-$(CONFIG_IRDA) += ../../drivers/staging/irda/net/
in a networking Makefile, can I? Does "../" even work in a Makefile
like that?
Any other thoughts?
> It's one thing if IRDA on it's own has deteriorated and broken in some
> ways over time due to lack of maintainence, it's another to knowingly
> do something to it that causes a regression which is what happened
> here.
It has deteriorated and is broken and does not work at all from the
reports I have gotten, Linus pointing this out to me directly due to his
involvement in irda-related dive computers. So I don't think anyone is
using this at all right now, it seems to crash when used anyway. So no
one is running this "build in" code at the moment :)
ideas?
thanks,
greg k-h
next prev parent reply other threads:[~2017-08-29 17:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-29 7:09 [PATCH net-next] staging: irda: update MAINTAINERS Greg Kroah-Hartman
2017-08-29 9:14 ` [PATCH net-next] staging: irda: force to be a kernel module Greg Kroah-Hartman
2017-08-29 16:35 ` David Miller
2017-08-29 17:26 ` Greg KH [this message]
2017-08-29 17:31 ` Greg KH
2017-08-29 17:46 ` [PATCH v2 net-next] irda: fix link order if IRDA is built into the kernel Greg KH
2017-08-29 17:49 ` David Miller
2017-08-29 19:05 ` Greg KH
2017-08-30 11:16 ` [PATCH v3 net-next] staging: irda: fix init level for irda core Greg KH
2017-08-30 17:15 ` David Miller
2017-08-29 17:40 ` [PATCH net-next] staging: irda: force to be a kernel module David Miller
2017-08-29 16:30 ` [PATCH net-next] staging: irda: update MAINTAINERS David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170829172608.GA4700@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=davem@davemloft.net \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=samuel@sortiz.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox