All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: handygewinnspiel@gmx.de, matthew@wil.cx,
	linux-kernel@vger.kernel.org, mchehab@infradead.org, rjw@sisk.pl,
	viro@zeniv.linux.org.uk, linux-fsdevel@vger.kernel.org,
	HWerner4@gmx.de, xfs mailing list <xfs@oss.sgi.com>,
	Christoph Hellwig <hch@lst.de>,
	stable@kernel.org, chris.mason@oracle.com
Subject: Re: [linux-dvb] compiling on 2.6.28 broken?
Date: Wed, 14 Jan 2009 15:48:40 -0600	[thread overview]
Message-ID: <496E5DB8.1030007@sandeen.net> (raw)
In-Reply-To: <20090114134417.e6b29b52.akpm@linux-foundation.org>

Andrew Morton wrote:
> On Wed, 14 Jan 2009 15:35:46 -0600
> Eric Sandeen <sandeen@sandeen.net> wrote:
> 
>> Chris Mason wrote:
>>> On Wed, 2009-01-14 at 22:19 +0100, wk wrote:
>> ...
>>>> I cannot fully understand what strace -v outputs (see attachment), but 
>>>> what i see is that 'find' stops after finding a file with d_off = 4294967295
>>>> 4294967295  =  0xFFFFFFFF, adding any number greater that zero will be 
>>>> greater that 32bits, so this could be the reason for the message "value 
>>>> too large".
>>>>
>>>>
>>>>
>>>> I also noticed that i cannot access these files through samba if i boot 
>>>> from 2.6.28 - really strange.
>>>> If i reboot older kernels these are visible in samba again and fully 
>>>> accessible.
>>>>
>>>> Attached the log from stracing the command which was ivoked by the 
>>>> Makefile from v4l-dvb.
>>>> I guess this is all i could contribute to that problem. Thats stuff for 
>>>> xfs filesystem experts now..
>>> Seems suspect indeed.  Could you please attach the strace for the run
>>> that works on the older kernel?
>> Chris got my attention on this one; you probably want this fix from hch:
>>
>> http://oss.sgi.com/archives/xfs/2009-01/msg00158.html
>>
> 
> Looks likely.  It is below, for anyone who would like to test it.
> 
> 
> It is in linux-next.  Guys, do we plan to merge this into 2.6.29?

It should be merged there, yes.  Was hoping that sgi would request that
soon....

> (cc's stable@kernel.org)
> 
> This patch applies OK to 2.6.27 and 2.6.28.  Is it also needed there? 
> If so, it should have had "Cc: <stable@kernel.org>" in the changelog so
> that it doesn't get lost.
> 

It is needed for .28, but should not be needed for .27 AFAIK.

-Eric

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

WARNING: multiple messages have this Message-ID (diff)
From: Eric Sandeen <sandeen@sandeen.net>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: chris.mason@oracle.com, handygewinnspiel@gmx.de, matthew@wil.cx,
	rjw@sisk.pl, HWerner4@gmx.de, viro@zeniv.linux.org.uk,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	mchehab@infradead.org, stable@kernel.org,
	Christoph Hellwig <hch@lst.de>, Lachlan McIlroy <lachlan@sgi.com>,
	xfs mailing list <xfs@oss.sgi.com>
Subject: Re: [linux-dvb] compiling on 2.6.28 broken?
Date: Wed, 14 Jan 2009 15:48:40 -0600	[thread overview]
Message-ID: <496E5DB8.1030007@sandeen.net> (raw)
In-Reply-To: <20090114134417.e6b29b52.akpm@linux-foundation.org>

Andrew Morton wrote:
> On Wed, 14 Jan 2009 15:35:46 -0600
> Eric Sandeen <sandeen@sandeen.net> wrote:
> 
>> Chris Mason wrote:
>>> On Wed, 2009-01-14 at 22:19 +0100, wk wrote:
>> ...
>>>> I cannot fully understand what strace -v outputs (see attachment), but 
>>>> what i see is that 'find' stops after finding a file with d_off = 4294967295
>>>> 4294967295  =  0xFFFFFFFF, adding any number greater that zero will be 
>>>> greater that 32bits, so this could be the reason for the message "value 
>>>> too large".
>>>>
>>>>
>>>>
>>>> I also noticed that i cannot access these files through samba if i boot 
>>>> from 2.6.28 - really strange.
>>>> If i reboot older kernels these are visible in samba again and fully 
>>>> accessible.
>>>>
>>>> Attached the log from stracing the command which was ivoked by the 
>>>> Makefile from v4l-dvb.
>>>> I guess this is all i could contribute to that problem. Thats stuff for 
>>>> xfs filesystem experts now..
>>> Seems suspect indeed.  Could you please attach the strace for the run
>>> that works on the older kernel?
>> Chris got my attention on this one; you probably want this fix from hch:
>>
>> http://oss.sgi.com/archives/xfs/2009-01/msg00158.html
>>
> 
> Looks likely.  It is below, for anyone who would like to test it.
> 
> 
> It is in linux-next.  Guys, do we plan to merge this into 2.6.29?

It should be merged there, yes.  Was hoping that sgi would request that
soon....

> (cc's stable@kernel.org)
> 
> This patch applies OK to 2.6.27 and 2.6.28.  Is it also needed there? 
> If so, it should have had "Cc: <stable@kernel.org>" in the changelog so
> that it doesn't get lost.
> 

It is needed for .28, but should not be needed for .27 AFAIK.

-Eric

  reply	other threads:[~2009-01-14 21:51 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090112190420.51f75853@pedra.chehab.org>
     [not found] ` <20090112132130.6c932b85.akpm@linux-foundation.org>
     [not found]   ` <20090112220624.4fbfee34@pedra.chehab.org>
     [not found]     ` <20090112162337.318dd61d.akpm@linux-foundation.org>
2009-01-13 18:47       ` [linux-dvb] compiling on 2.6.28 broken? handygewinnspiel
2009-01-13 18:47         ` handygewinnspiel
2009-01-13 18:59         ` Andrew Morton
2009-01-13 19:17           ` handygewinnspiel
2009-01-13 19:37             ` Andrew Morton
2009-01-13 20:02               ` handygewinnspiel
2009-01-13 20:02                 ` handygewinnspiel
2009-01-13 20:38               ` Matthew Wilcox
2009-01-14 18:29                 ` Chris Mason
2009-01-14 21:19                   ` wk
2009-01-14 21:24                     ` Chris Mason
2009-01-14 21:35                       ` Eric Sandeen
2009-01-14 21:40                         ` Chris Mason
2009-01-14 23:00                           ` Kay Sievers
2009-01-15  1:54                             ` Chris Mason
2009-01-14 21:41                         ` Eric Sandeen
2009-01-14 21:41                           ` Eric Sandeen
2009-01-14 21:44                         ` Andrew Morton
2009-01-14 21:48                           ` Eric Sandeen [this message]
2009-01-14 21:48                             ` Eric Sandeen
2009-01-14 22:57                             ` Lachlan McIlroy
2009-01-14 22:57                               ` Lachlan McIlroy
2009-01-18 22:06                             ` Christoph Hellwig
2009-01-18 22:06                               ` Christoph Hellwig
2009-01-14 21:41                       ` wk
2009-01-14 22:30                     ` Dave Chinner
2009-01-15 19:41                       ` wk
2009-01-15 19:41                         ` wk
2009-01-15 22:23                         ` Dave Chinner
2009-01-10 10:27 handygewinnspiel
     [not found] ` <20090110103700.107530@gmx.net>
2009-01-10 11:07   ` wk
2009-01-10 18:21     ` wk
2009-01-12  5:49       ` Mauro Carvalho Chehab

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=496E5DB8.1030007@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=HWerner4@gmx.de \
    --cc=akpm@linux-foundation.org \
    --cc=chris.mason@oracle.com \
    --cc=handygewinnspiel@gmx.de \
    --cc=hch@lst.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew@wil.cx \
    --cc=mchehab@infradead.org \
    --cc=rjw@sisk.pl \
    --cc=stable@kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    --cc=xfs@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.