linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: wk <handygewinnspiel@gmx.de>
To: wk <handygewinnspiel@gmx.de>,
	Chris Mason <chris.mason@oracle.com>,
	Matthew Wilcox <matthew@wil.cx>,
	Andrew Morton <akpm@linux-foundation.org>,
	rjw@sisk.pl, HWerner4@gmx.de, viro@zeni
Subject: Re: [linux-dvb] compiling on 2.6.28 broken?
Date: Thu, 15 Jan 2009 20:41:40 +0100	[thread overview]
Message-ID: <496F9174.5080907@gmx.de> (raw)
In-Reply-To: <20090114223016.GY8071@disturbed>

Dave Chinner wrote:
> On Wed, Jan 14, 2009 at 10:19:39PM +0100, wk wrote:
>   
>> Chris Mason 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..
>>     
>
> It's obviously the regression fixed by:
>
> http://oss.sgi.com/cgi-bin/gitweb.cgi?p=xfs/xfs.git;a=commit;h=15440319767942a363f282d6585303d3d75088ba
>
> It needs to be pushed to Linus, then into 2.6.28-stable.
>
> Cheers,
>
> Dave.
>   

Yes, that solves the problems as expected. But may i kindly ask the xfs 
fs developers to put some more readable patch here,
so that its better understandable by looking at the source code? I think 
some macro would be better here, for example i used

#define TRUNC_TO_SIGNED32(x) (x & 0x7FFFFFFF)

inside xfs.h and replaced all "foo & 0x7fffffff" with 
"TRUNC_TO_SIGNED32(foo)".

Thanks for your help,
Winfried

  reply	other threads:[~2009-01-15 19:42 UTC|newest]

Thread overview: 22+ 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: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: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:44                         ` Andrew Morton
2009-01-14 21:48                           ` Eric Sandeen
2009-01-14 22:57                             ` Lachlan McIlroy
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 [this message]
2009-01-15 22:23                         ` Dave Chinner

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=496F9174.5080907@gmx.de \
    --to=handygewinnspiel@gmx.de \
    --cc=HWerner4@gmx.de \
    --cc=akpm@linux-foundation.org \
    --cc=chris.mason@oracle.com \
    --cc=matthew@wil.cx \
    --cc=rjw@sisk.pl \
    --cc=viro@zeni \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).