[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20121129183207.GA4688@kroah.com>
Date: Thu, 29 Nov 2012 10:32:07 -0800
From: Greg KH <gregkh@...uxfoundation.org>
To: Chen Gang <gang.chen@...anux.com>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
linux-serial@...r.kernel.org
Subject: Re: [Suggestion] drivers/tty: drivers/char/: for
MAX_ASYNC_BUFFER_SIZE
On Thu, Nov 29, 2012 at 01:57:59PM +0800, Chen Gang wrote:
> > And, I really don't understand here, why do you want to change this?
> > What is it going to change? And why?
> >
>
> Why:
> for the context MGSLPC_INFO *info in drivers/char/pcmcia/synclink_cs.c
> info->max_frame_size can be the value between 4096 .. 65535 (can be
> set by its module input parameter)
> info->flag_buf length is 4096 (MAX_ASYNC_BUFFER_SIZE)
> in function rx_get_frame
> the framesize is limit by info->max_frame_size, but may still be
> larger that 4096.
> when call function ldisc_receive_buf, info->flag_buf is equal to
> 4096, but framesize can be more than 4096. it will cause memory over flow.
Do you use that pcmcia driver for anything? Are those cards still
around?
> What:
> #define MAX_ASYNC_BUFFER_SIZE 0x10000 (instead of 4096, originally).
> let it match the max frame size.
>
> At last:
> my suggestion may be incorrect, need relative member (who expert about
> it) to help checking.
That driver might be incorrect, yes, care to make up a patch for it and
test it to verify it fixes the problem?
thanks,
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists