linux-kernel - RE: [char-misc-next 2/3] mei: fix reading large reposnes

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]

Message-ID: <5B8DA87D05A7694D9FA63FD143655C1B01F022F4@HASMSX106.ger.corp.intel.com>
Date:	Fri, 19 Apr 2013 18:59:49 +0000
From:	"Winkler, Tomas" <tomas.winkler@...el.com>
To:	Greg KH <gregkh@...uxfoundation.org>
CC:	"arnd@...db.de" <arnd@...db.de>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [char-misc-next 2/3] mei: fix reading large reposnes

> 
> On Fri, Apr 19, 2013 at 09:16:54PM +0300, Tomas Winkler wrote:
> > While writting to device is limitted to max_msg_length advertized in
> > client properites the read can be much longer delivered consequiting
> chunks.
> >
> > We use krealloc to enlarge the buffer when needed.
> >
> > Signed-off-by: Tomas Winkler <tomas.winkler@...el.com>
> 
> Patch 1/3 had some fuzz in interrupt.c, so I fixed that up by hand, but this
> one just fails to apply at all:
> 	checking file drivers/misc/mei/bus.c
> 	checking file drivers/misc/mei/client.c
> 	checking file drivers/misc/mei/client.h
> 	checking file drivers/misc/mei/interrupt.c
> 	Hunk #1 FAILED at 145.
> 	1 out of 1 hunk FAILED
> 	checking file drivers/misc/mei/main.c
> 
> So something is out of sync between us.
> 
> Care to refresh this patch based on my latest tree, and 3/3, and resend
> them?
Grrr,  I sent you one patch less, I've rebased this new spelling fix and missed to count it in.
I'm resending the missing patches.

Tomas 

--
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/