From: Tilman Schmidt <tilman@imap.cc>
To: David Miller <davem@davemloft.net>
Cc: dan.carpenter@oracle.com, isdn@linux-pingi.de,
yoshfuji@linux-ipv6.org, netdev@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [patch] isdnloop: several buffer overflows
Date: Thu, 10 Apr 2014 11:16:52 +0000 [thread overview]
Message-ID: <1397128612.21813.104938677.2F2327F5@webmail.messagingengine.com> (raw)
In-Reply-To: <20140408.124253.1716775944053750290.davem@davemloft.net>
On Tue, Apr 8, 2014, at 18:42, David Miller wrote:
>
> Applied and queued up for -stable, thanks.
>
> This thing is marked broken-on-smp so the impact is very close to zero.
isdnloop is a loopback test driver for the deprecated old ISDN4Linux
subsystem.
I doubt anyone is still interested in it.
--
Tilman Schmidt
tilman@imap.cc
prev parent reply other threads:[~2014-04-10 11:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-08 9:23 [patch] isdnloop: several buffer overflows Dan Carpenter
2014-04-08 9:34 ` David Laight
2014-04-08 11:02 ` Dan Carpenter
2014-04-08 16:42 ` David Miller
2014-04-10 11:16 ` Tilman Schmidt [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=1397128612.21813.104938677.2F2327F5@webmail.messagingengine.com \
--to=tilman@imap.cc \
--cc=dan.carpenter@oracle.com \
--cc=davem@davemloft.net \
--cc=isdn@linux-pingi.de \
--cc=kernel-janitors@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.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