linux-kernel - Re: fs,seq_file: huge allocations for seq file reads

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] [day] [month] [year] [list]

Date:	Tue, 08 Apr 2014 10:51:27 -0400
From:	Sasha Levin <sasha.levin@...cle.com>
To:	Dave Jones <davej@...hat.com>,
	linux-fsdevel <linux-fsdevel@...r.kernel.org>,
	Al Viro <viro@...IV.linux.org.uk>,
	LKML <linux-kernel@...r.kernel.org>, Greg KH <greg@...ah.com>
Subject: Re: fs,seq_file: huge allocations for seq file reads

On 04/08/2014 10:49 AM, Dave Jones wrote:
> On Tue, Apr 08, 2014 at 10:45:31AM -0400, Sasha Levin wrote:
>  
>  > It seems that when we attempt to read huge chunks of data from a seq file
>  > there would be no check for the size being read, leading to the kernel
>  > attempting to allocate huge chunks of data internally.
>  > 
>  > As far as I remember, there was a PAGE_SIZE limitation on those, but I'm
>  > not certain about that. Could someone please confirm it?
> 
> I've had this diff sitting around for a while to figure out which
> seq_file we're talking about.  I think Al wrote it, I forget..

I'll add it in.

I didn't realize it was a problem with a specific file, I thought it was
an issue with seq files in general.


Thanks,
Sasha
--
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/