public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: nardelli <jnardelli@infosciences.com>
To: root@chaos.analogic.com
Cc: Greg KH <greg@kroah.com>, Ian Abbott <abbotti@mev.co.uk>,
	linux-kernel@vger.kernel.org,
	linux-usb-devel@lists.sourceforge.net
Subject: Re: [PATCH] Memory leak in visor.c and ftdi_sio.c
Date: Mon, 07 Jun 2004 11:56:58 -0400	[thread overview]
Message-ID: <40C4904A.2080903@infosciences.com> (raw)
In-Reply-To: <Pine.LNX.4.53.0406071141090.10324@chaos>

Richard B. Johnson wrote:
> On Mon, 7 Jun 2004, nardelli wrote:
> 
> 
>>Greg KH wrote:
>>
>>>On Fri, Jun 04, 2004 at 05:34:41PM +0100, Ian Abbott wrote:
>>>
>>>
>>>>On 04/06/2004 15:59, nardelli wrote:
> 
> [SNIPPED...]
> 
> 
>>>
>>>===== drivers/usb/serial/visor.c 1.114 vs edited =====
>>>--- 1.114/drivers/usb/serial/visor.c	Fri Jun  4 07:13:10 2004
>>>+++ edited/drivers/usb/serial/visor.c	Fri Jun  4 17:12:53 2004
>>
>>...
>>
>>Just curious - is there something special about 42?  Grepping wasn't
>>very useful, as numbers like this are scattered all over the place.
>>
>>
>>>+/* number of outstanding urbs to prevent userspace DoS from happening */
>>>+#define URB_UPPER_LIMIT	42
> 
> 
> See Hitchiker's Guide to the Galaxy. ;^
> 

LOL - I knew I shouldn't have asked :-)


-- 
Joe Nardelli
jnardelli@infosciences.com

  reply	other threads:[~2004-06-07 15:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-04 14:59 [PATCH] Memory leak in visor.c and ftdi_sio.c nardelli
2004-06-04 16:34 ` Ian Abbott
2004-06-04 17:25   ` nardelli
2004-06-04 18:04   ` Pete Zaitcev
2004-06-04 23:16   ` [linux-usb-devel] " Peter Horton
2004-06-05  0:18   ` Greg KH
2004-06-07  9:58     ` Ian Abbott
2004-06-07 14:19     ` nardelli
2004-06-07 15:43       ` Richard B. Johnson
2004-06-07 15:56         ` nardelli [this message]
2004-06-04 18:12 ` Greg KH
2004-06-04 18:47   ` nardelli
2004-06-04 22:02     ` Greg KH

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=40C4904A.2080903@infosciences.com \
    --to=jnardelli@infosciences.com \
    --cc=abbotti@mev.co.uk \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=root@chaos.analogic.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox