On Mon, 2016-04-25 at 16:10 +0300, Pekka Paalanen wrote:
> In the mean time, Marek's patch gets my
> Reviewed-by: Pekka Paalanen
> because it is an improvement for many (most?) systems.
Yeah, looks good to me.
remote: I: patch #83402 updated using rev
On Mon, Apr 25, 2016 at 02:40:31PM +0200, Marek Chalupa wrote:
>
> On 04/25/16 12:20, Pekka Paalanen wrote:
> > On Mon, 25 Apr 2016 11:33:00 +0200
> > Marek Chalupa wrote:
> >
> >> If posix_fallocate or ftruncate is interrupted by signal
> >> while working, we return -1 as
On Mon, 25 Apr 2016 15:56:58 +0300
Ian Ray wrote:
> On Mon, Apr 25, 2016 at 02:40:31PM +0200, Marek Chalupa wrote:
> >
> > On 04/25/16 12:20, Pekka Paalanen wrote:
> > > On Mon, 25 Apr 2016 11:33:00 +0200
> > > Marek Chalupa wrote:
> > >
> > >> If
On 04/25/16 12:20, Pekka Paalanen wrote:
> On Mon, 25 Apr 2016 11:33:00 +0200
> Marek Chalupa wrote:
>
>> If posix_fallocate or ftruncate is interrupted by signal
>> while working, we return -1 as fd and the allocation process
>> returns BadAlloc error. That causes xwayland
On Mon, 25 Apr 2016 11:33:00 +0200
Marek Chalupa wrote:
> If posix_fallocate or ftruncate is interrupted by signal
> while working, we return -1 as fd and the allocation process
> returns BadAlloc error. That causes xwayland clients to abort
> with 'BadAlloc (insufficient
If posix_fallocate or ftruncate is interrupted by signal
while working, we return -1 as fd and the allocation process
returns BadAlloc error. That causes xwayland clients to abort
with 'BadAlloc (insufficient resources for operation)'
even when there's a lot of resources available.
Fix it by