From: Arnd Bergmann <arnd@arndb.de>
To: David Miller <davem@davemloft.net>
Cc: khc@pm.waw.pl, gregkh <gregkh@linuxfoundation.org>,
driverdevel <devel@driverdev.osuosl.org>,
Networking <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Eric Biggers <ebiggers@kernel.org>,
Andrew Hendry <andrew.hendry@gmail.com>,
linux-x25@vger.kernel.org,
Kevin Curtis <kevin.curtis@farsite.com>,
"R.J.Dunlop" <bob.dunlop@farsite.com>,
Qiang Zhao <qiang.zhao@nxp.com>, Martin Schiller <ms@dev.tdt.de>
Subject: Re: [PATCH 4/4] [RFC] staging/net: move AF_X25 into drivers/staging
Date: Mon, 9 Dec 2019 20:26:56 +0100 [thread overview]
Message-ID: <CAK8P3a25UGV1KS1ufZsyQJk1+9Rp9is0x6eOU7pr5Xf6Z3N2gA@mail.gmail.com> (raw)
In-Reply-To: <20191209.102950.2248756181772063368.davem@davemloft.net>
On Mon, Dec 9, 2019 at 7:29 PM David Miller <davem@davemloft.net> wrote:
>
> From: Arnd Bergmann <arnd@arndb.de>
> Date: Mon, 9 Dec 2019 16:12:56 +0100
>
> > syzbot keeps finding issues in the X.25 implementation that nobody is
> > interested in fixing. Given that all the x25 patches of the past years
> > that are not global cleanups tend to fix user-triggered oopses, is it
> > time to just retire the subsystem?
>
> I have a bug fix that I'm currently applying to 'net' right now actually:
>
> https://patchwork.ozlabs.org/patch/1205973/
>
> So your proposal might be a bit premature.
Ok, makes sense. Looking back in the history, I also see other bugfixes
from the same author.
Adding Martin Schiller to Cc: for a few questions:
- What hardware are you using for X.25?
- Would you be available to be listed in the MAINTAINERS file
as a contact for net/x25?
- Does your bug fix address the latest issue found by syzbot[1],
or do you have an idea to fix it if not?
Arnd
[1] https://lore.kernel.org/netdev/CAK8P3a0LdF+aQ1hnZrVKkNBQaum0WqW1jyR7_Eb+JRiwyHWr6Q@mail.gmail.com/
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: David Miller <davem@davemloft.net>
Cc: driverdevel <devel@driverdev.osuosl.org>,
Martin Schiller <ms@dev.tdt.de>,
linux-x25@vger.kernel.org, gregkh <gregkh@linuxfoundation.org>,
"R.J.Dunlop" <bob.dunlop@farsite.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Kevin Curtis <kevin.curtis@farsite.com>,
Eric Biggers <ebiggers@kernel.org>,
Networking <netdev@vger.kernel.org>,
Andrew Hendry <andrew.hendry@gmail.com>,
Qiang Zhao <qiang.zhao@nxp.com>,
khc@pm.waw.pl
Subject: Re: [PATCH 4/4] [RFC] staging/net: move AF_X25 into drivers/staging
Date: Mon, 9 Dec 2019 20:26:56 +0100 [thread overview]
Message-ID: <CAK8P3a25UGV1KS1ufZsyQJk1+9Rp9is0x6eOU7pr5Xf6Z3N2gA@mail.gmail.com> (raw)
In-Reply-To: <20191209.102950.2248756181772063368.davem@davemloft.net>
On Mon, Dec 9, 2019 at 7:29 PM David Miller <davem@davemloft.net> wrote:
>
> From: Arnd Bergmann <arnd@arndb.de>
> Date: Mon, 9 Dec 2019 16:12:56 +0100
>
> > syzbot keeps finding issues in the X.25 implementation that nobody is
> > interested in fixing. Given that all the x25 patches of the past years
> > that are not global cleanups tend to fix user-triggered oopses, is it
> > time to just retire the subsystem?
>
> I have a bug fix that I'm currently applying to 'net' right now actually:
>
> https://patchwork.ozlabs.org/patch/1205973/
>
> So your proposal might be a bit premature.
Ok, makes sense. Looking back in the history, I also see other bugfixes
from the same author.
Adding Martin Schiller to Cc: for a few questions:
- What hardware are you using for X.25?
- Would you be available to be listed in the MAINTAINERS file
as a contact for net/x25?
- Does your bug fix address the latest issue found by syzbot[1],
or do you have an idea to fix it if not?
Arnd
[1] https://lore.kernel.org/netdev/CAK8P3a0LdF+aQ1hnZrVKkNBQaum0WqW1jyR7_Eb+JRiwyHWr6Q@mail.gmail.com/
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
next prev parent reply other threads:[~2019-12-09 19:27 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-09 15:12 [PATCH 1/4] [net-next] wan: remove stale Kconfig entries Arnd Bergmann
2019-12-09 15:12 ` Arnd Bergmann
2019-12-09 15:12 ` [PATCH 2/4] [net-next] wan: remove sbni/granch driver Arnd Bergmann
2019-12-09 15:12 ` Arnd Bergmann
2019-12-09 15:12 ` [PATCH 3/4] [net-next] wan: remove old frame relay driver Arnd Bergmann
2019-12-09 15:12 ` Arnd Bergmann
2019-12-09 15:12 ` [PATCH 4/4] [RFC] staging/net: move AF_X25 into drivers/staging Arnd Bergmann
2019-12-09 15:12 ` Arnd Bergmann
2019-12-09 15:41 ` Greg Kroah-Hartman
2019-12-09 15:41 ` Greg Kroah-Hartman
2019-12-09 18:29 ` David Miller
2019-12-09 18:29 ` David Miller
2019-12-09 19:26 ` Arnd Bergmann [this message]
2019-12-09 19:26 ` Arnd Bergmann
2019-12-10 8:59 ` Martin Schiller
2019-12-10 8:59 ` Martin Schiller
2019-12-10 13:51 ` Arnd Bergmann
2019-12-10 13:51 ` Arnd Bergmann
2019-12-11 5:58 ` Martin Schiller
2019-12-11 5:58 ` Martin Schiller
2019-12-11 7:10 ` Krzysztof Hałasa
2019-12-11 7:10 ` Krzysztof Hałasa
2019-12-11 7:10 ` Krzysztof Hałasa
2019-12-11 13:34 ` Andrew Lunn
2019-12-11 13:34 ` Andrew Lunn
2019-12-11 13:34 ` Andrew Lunn
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=CAK8P3a25UGV1KS1ufZsyQJk1+9Rp9is0x6eOU7pr5Xf6Z3N2gA@mail.gmail.com \
--to=arnd@arndb.de \
--cc=andrew.hendry@gmail.com \
--cc=bob.dunlop@farsite.com \
--cc=davem@davemloft.net \
--cc=devel@driverdev.osuosl.org \
--cc=ebiggers@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kevin.curtis@farsite.com \
--cc=khc@pm.waw.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-x25@vger.kernel.org \
--cc=ms@dev.tdt.de \
--cc=netdev@vger.kernel.org \
--cc=qiang.zhao@nxp.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.