lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190128165318.GA16213@kroah.com>
Date:   Mon, 28 Jan 2019 17:53:18 +0100
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Martin Kepplinger <martink@...teo.de>
Cc:     jslaby@...e.com, linux-kernel@...r.kernel.org,
        Manfred Schlaegl <manfred.schlaegl@...zinger.com>,
        Martin Kepplinger <martin.kepplinger@...zinger.com>
Subject: Re: [PATCH] tty: increase the default flip buffer limit to 2*640K

On Mon, Jan 28, 2019 at 05:38:43PM +0100, Martin Kepplinger wrote:
> From: Manfred Schlaegl <manfred.schlaegl@...zinger.com>
> 
> The default value for this was 64K. We increase this by a factor of
> 10 to 640K to prevent data loss when using fast serial interfaces.

What fast serial interface are you using where you run into this limit?

> Since this value is only a maximum limit for allocation and isn't used
> by default, this change has minimal effect on systems with slow interfaces.

So what systems does it affect?

> Signed-off-by: Manfred Schlaegl <manfred.schlaegl@...zinger.com>
> Signed-off-by: Martin Kepplinger <martin.kepplinger@...zinger.com>
> ---
> 
> Is there any reason for this _limit_ to be as small as 64K?

Historical mostly from what I can tell.

thanks,

greg k-h

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ