From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Cc: Ranulf Doswell <ralf@ranulf.net>, cbe-oss-dev@ozlabs.org
Subject: Re: [Bluez-devel] [Cbe-oss-dev] [PATCH] bluetooth: reset unexpected connections
Date: Thu, 05 Jul 2007 10:11:57 +0200 [thread overview]
Message-ID: <1183623117.6351.87.camel@aeonflux.holtmann.net> (raw)
In-Reply-To: <Pine.LNX.4.62.0707041155540.11471@pademelon.sonytel.be>
Hi Geert,
> > Do you have any suggestions of an alternative approach to handling this
> > error condition rather than just filling up the syslog? It's definitely a
> > very real DOS possibility - my syslog was growing by about 1Mb per minute
> > with just two regular controllers. Someone who deliberately constructed a
> > device to bombard a linux box with junk bluetooth data could probably fill
> > someone's /var partition in a matter of hours.
>
> Perhaps you can replace the call to printk() with a call to printk_ratelimit()?
we could. Feel free to send a patch for it.
Regards
Marcel
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2007-07-05 8:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-02 19:04 [Bluez-devel] [PATCH] bluetooth: reset unexpected connections Ranulf Doswell
2007-07-03 3:28 ` Marcel Holtmann
2007-07-03 18:26 ` [Cbe-oss-dev] " Geoff Levand
2007-07-03 19:38 ` Ranulf Doswell
2007-07-04 1:55 ` Marcel Holtmann
2007-07-04 7:05 ` [Cbe-oss-dev] " Ranulf Doswell
2007-07-04 9:56 ` [Bluez-devel] [Cbe-oss-dev] " Geert Uytterhoeven
2007-07-05 8:11 ` Marcel Holtmann [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=1183623117.6351.87.camel@aeonflux.holtmann.net \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=cbe-oss-dev@ozlabs.org \
--cc=ralf@ranulf.net \
/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