From: Joe Perches <joe@perches.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Stephen Hemminger <stephen@networkplumber.org>,
davem@davemloft.net, pablo@netfilter.org,
kadlec@blackhole.kfki.hu, fw@strlen.de,
devel@driverdev.osuosl.org,
linux-decnet-user@lists.sourceforge.net, netdev@vger.kernel.org,
netfilter-devel@vger.kernel.org, coreteam@netfilter.org,
Stephen Hemminger <sthemmin@microsoft.com>
Subject: Re: [PATCH net-next v2] net: move decnet to staging
Date: Tue, 14 Nov 2017 07:07:13 -0800 [thread overview]
Message-ID: <1510672033.2006.1.camel@perches.com> (raw)
In-Reply-To: <1510604753.2849.154.camel@edumazet-glaptop3.roam.corp.google.com>
On Mon, 2017-11-13 at 12:25 -0800, Eric Dumazet wrote:
> On Mon, 2017-11-13 at 11:32 -0800, Joe Perches wrote:
> > On Mon, 2017-11-13 at 09:11 -0800, Stephen Hemminger wrote:
> > > Support for Decnet has been orphaned for some time.
> > > In the interest of reducing the potential bug surface and pre-holiday
> > > cleaning, move the decnet protocol into staging for eventual removal.
> >
> > []
> > > diff --git a/drivers/staging/decnet/TODO b/drivers/staging/decnet/TODO
> >
> > []
> > > @@ -0,0 +1,4 @@
> > > +The DecNet code will be removed soon from the kernel tree as it is old,
> > > +obsolete, and buggy.
> >
> > Old and obsolete, well OK, but
> > what's buggy about decnet?
> >
> > https://bugzilla.kernel.org/buglist.cgi?quicksearch=decnet
> >
> > Zarro Boogs found.
> >
>
> Then that means nobody uses it.
No, it doesn't mean that.
> And that syzkaller guys never bothered to add code to actually trigger
> the bugs that are probably there. Probably they have bigger fishes to
> fry at this moment.
It may mean that.
> If we leave the code there, chances are high that some hacker is
> interested into exploiting the bugs.
linux isn't bsd.
The code is there already.
prev parent reply other threads:[~2017-11-14 15:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-13 17:11 [PATCH net-next v2] net: move decnet to staging Stephen Hemminger
2017-11-13 19:32 ` Joe Perches
2017-11-13 20:25 ` Eric Dumazet
2017-11-14 15:07 ` Joe Perches [this message]
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=1510672033.2006.1.camel@perches.com \
--to=joe@perches.com \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=devel@driverdev.osuosl.org \
--cc=eric.dumazet@gmail.com \
--cc=fw@strlen.de \
--cc=kadlec@blackhole.kfki.hu \
--cc=linux-decnet-user@lists.sourceforge.net \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=stephen@networkplumber.org \
--cc=sthemmin@microsoft.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.