reiser4 snapshot for August 26th.

reiser4 snapshot for August 26th.

[Oleg Drokin]

Hello!

   I have just released another reiser4 snapshot that I hope all interested
   parties will try. It is released against 2.6.0-test4.
   You can find it at http://namesys.com/snapshots/2003.08.26
   I include release notes below.

Reiser4 snapshot for 2003.08.26

WARNING!!! This code is experimental! WE ARE NOT KIDDING! DO NOT PUT
ANY VALUABLE DATA ON REISER4 YET!

Fixed some bugs. And finally reiser4 should compile on 64bit boxes (hm. somebody try it,
as I am unable to build any 2.6 kernel for ia64). Also reiser4 should now build without
debug enabled.
Important SMP bug was fixed (only was in effect for SMP kernels on boxes with less than 3 CPUs).
There are still some OOM problems sometimes that we are working on, but generally
I hope problems reported by various people about compile failures should be fixed now.
Readonly mounts (and hence - reiser4 as rootfs) are not supported too.

reiser4progs update includes some 64 bit fixes too along with other stuff.
fsck still does not work, so don't even try to run it.

Snapshot is released as a patch against linux-2.6.0-test4
REISER4_NOOPT config option (Disable compiler optimizations for reiser4 code.)
is known to not compile on x86.
Enable CONFIG_REISER4_LARGE_KEY, as reiser4progs are creating filesystems with
large keys by default.
The reiser4-kernelonly.diff file represents only required kernel modifications if you plan to use our reiser4 bk repository.
    It does not contains any reiser4 code
The reiser4.diff is full patch with everything included.

Changelog (extracted by "bk changes"):

ChangeSet@1.1218.1.2, 2003-08-26 12:53:59+04:00, god@laputa.namesys.com
  remove assertion (contradicts recent changes in prepare_twig_cut())

ChangeSet@1.1218.1.1, 2003-08-26 12:53:28+04:00, god@laputa.namesys.com
  remove superfluous check

ChangeSet@1.1217.1.3, 2003-08-26 11:19:03+04:00, zam@crimson.namesys.com
  search_one_bitmap_backward() endless loop fix.

ChangeSet@1.1216.1.1, 2003-08-25 22:01:52+04:00, zam@crimson.namesys.com
  backward search bitmap code fixes

ChangeSet@1.1217.1.1, 2003-08-25 21:26:46+04:00, edward@theta.namesys.com
  ctail.c:
    Fixed bug
  file.c:
    shared reserve_cut_iteration
  cryptcompress.c:
    Added cut_items_cryptcompress(), 
    fixed bugs 

ChangeSet@1.1215.1.6, 2003-08-25 21:06:06+04:00, god@laputa.namesys.com
  sync with recent change in prepare_twig_cut()

ChangeSet@1.1215.1.5, 2003-08-25 21:00:04+04:00, god@laputa.namesys.com
  when removing eottl, clear connected bits on formatted neighbors

ChangeSet@1.1215.1.4, 2003-08-25 20:59:26+04:00, god@laputa.namesys.com
  restore old check.

ChangeSet@1.1215.1.3, 2003-08-25 20:59:13+04:00, god@laputa.namesys.com
  fix race in check_jload()

ChangeSet@1.1215.1.2, 2003-08-25 20:58:52+04:00, god@laputa.namesys.com
  add separate inode to keep bitmaps.
  cleanup

ChangeSet@1.1215.1.1, 2003-08-25 20:45:18+04:00, god@laputa.namesys.com
  fix fence error in wake_up_requestor()

ChangeSet@1.1216, 2003-08-25 18:05:17+04:00, green@angband.namesys.com
  bitmap.c:
    Remove erroneous ON_DEBUG()

ChangeSet@1.1215, 2003-08-25 13:58:15+04:00, god@laputa.namesys.com
  use vmalloc instead of kmalloc

ChangeSet@1.1208.1.1, 2003-08-25 08:49:07+04:00, zam@crimson.namesys.com
  bitmap code reorganization

ChangeSet@1.1213, 2003-08-24 15:56:24+04:00, green@angband.namesys.com
  inode.h:
    64bit compile fix

ChangeSet@1.1212, 2003-08-22 21:05:40+04:00, god@laputa.namesys.com
  fix compilation errors

ChangeSet@1.1211, 2003-08-22 21:00:56+04:00, god@laputa.namesys.com
  restore compilability.

ChangeSet@1.1210, 2003-08-22 20:56:38+04:00, god@laputa.namesys.com
  fix problems with BK's handling of symlinks

ChangeSet@1.1209, 2003-08-22 20:55:24+04:00, god@laputa.namesys.com
  Merge laputa.namesys.com:/home/god/projects/2.5/fs/reiser4
  into laputa.namesys.com:/home/god/projects/i386/fs/reiser4

ChangeSet@1.1185.1.17, 2003-08-22 20:45:52+04:00, god@laputa.namesys.com
  cleanup

ChangeSet@1.1185.1.16, 2003-08-22 20:45:32+04:00, god@laputa.namesys.com
  add scripts to perform mongo automatically.

ChangeSet@1.1185.1.15, 2003-08-22 20:44:24+04:00, god@laputa.namesys.com
  fix race in sibling list code.

ChangeSet@1.1185.1.14, 2003-08-22 20:43:54+04:00, god@laputa.namesys.com
  fix debugging checks.

ChangeSet@1.1185.1.13, 2003-08-22 20:43:15+04:00, god@laputa.namesys.com
  don't do read-ahead if low on memory.

ChangeSet@1.1185.1.12, 2003-08-22 20:42:55+04:00, god@laputa.namesys.com
  add assertion.

ChangeSet@1.1185.1.11, 2003-08-22 20:42:39+04:00, god@laputa.namesys.com
  fix assertion: atom lock should be held to avoid races with fusion.

ChangeSet@1.1185.1.10, 2003-08-22 20:42:13+04:00, god@laputa.namesys.com
  use jnode attached to page to avoid hash table lookup when possible

ChangeSet@1.1185.1.9, 2003-08-22 20:41:38+04:00, god@laputa.namesys.com
  add sysfs file with a list of all active atoms.

ChangeSet@1.1185.1.8, 2003-08-22 20:40:59+04:00, god@laputa.namesys.com
  don't set JNODE_DKSET in add_empty_leaf() to avoid races

ChangeSet@1.1185.1.7, 2003-08-22 20:40:23+04:00, god@laputa.namesys.com
  move check.

ChangeSet@1.1185.1.6, 2003-08-22 20:40:08+04:00, god@laputa.namesys.com
  fix race in eflush_del().
  fix hash function.
  make hash table dynamically sized.

ChangeSet@1.1185.1.5, 2003-08-22 20:39:29+04:00, god@laputa.namesys.com
  mark get_current_context() as const.

ChangeSet@1.1185.1.4, 2003-08-22 20:39:06+04:00, god@laputa.namesys.com
  remove noisy compiler options

Re: reiser4 snapshot for August 26th.

[Steven Cole]

On Tue, 2003-08-26 at 04:22, Oleg Drokin wrote:
> Hello!
> 
>    I have just released another reiser4 snapshot that I hope all interested
>    parties will try. It is released against 2.6.0-test4.
>    You can find it at http://namesys.com/snapshots/2003.08.26
>    I include release notes below.
> 
> Reiser4 snapshot for 2003.08.26
> 

I got this error while attempting to compile with reiser4.
Snippet from .config follows.

Steven

  CC      fs/reiser4/plugin/file/tail_conversion.o
  CC      fs/reiser4/sys_reiser4.o
fs/reiser4/sys_reiser4.c:54:32: parser/parser.code.c: No such file or directory
fs/reiser4/sys_reiser4.c: In function `sys_reiser4':
fs/reiser4/sys_reiser4.c:75: warning: implicit declaration of function `reiser4_pars_init'
fs/reiser4/sys_reiser4.c:75: warning: assignment makes pointer from integer without a cast
fs/reiser4/sys_reiser4.c:80: error: dereferencing pointer to incomplete type
fs/reiser4/sys_reiser4.c:82: warning: implicit declaration of function `yyparse'
fs/reiser4/sys_reiser4.c:83: warning: implicit declaration of function `reiser4_pars_free'
fs/reiser4/sys_reiser4.c:66: warning: unused variable `Gencode'
fs/reiser4/sys_reiser4.c: At top level:
fs/reiser4/parser/parser.h:333: warning: `Fistmsg' defined but not used
fs/reiser4/parser/parser.h:342: warning: `typesOfCommand' defined but not used
fs/reiser4/parser/parser.h:354: warning: `Code' defined but not used
make[2]: *** [fs/reiser4/sys_reiser4.o] Error 1
make[1]: *** [fs/reiser4] Error 2
make: *** [fs] Error 2
[steven@spc1 linux-2.6.0-test4-r4]$ grep REISER4 .config
CONFIG_REISER4_FS=y
CONFIG_REISER4_FS_SYSCALL=y
CONFIG_REISER4_LARGE_KEY=y
# CONFIG_REISER4_CHECK is not set
CONFIG_REISER4_USE_EFLUSH=y
# CONFIG_REISER4_BADBLOCKS is not set

Re: reiser4 snapshot for August 26th.

[Alex Zarochentsev]

On Tue, Aug 26, 2003 at 12:20:38PM -0600, Steven Cole wrote:
> On Tue, 2003-08-26 at 04:22, Oleg Drokin wrote:
> > Hello!
> > 
> >    I have just released another reiser4 snapshot that I hope all interested
> >    parties will try. It is released against 2.6.0-test4.
> >    You can find it at http://namesys.com/snapshots/2003.08.26
> >    I include release notes below.
> > 
> > Reiser4 snapshot for 2003.08.26
> > 
> 
> I got this error while attempting to compile with reiser4.
> Snippet from .config follows.

Disable "reiser4 system call" (CONFIG_REISER4_FS_SYSCALL) support, it is 
not ready.

> 
> Steven
> 
>   CC      fs/reiser4/plugin/file/tail_conversion.o
>   CC      fs/reiser4/sys_reiser4.o
> fs/reiser4/sys_reiser4.c:54:32: parser/parser.code.c: No such file or directory
> fs/reiser4/sys_reiser4.c: In function `sys_reiser4':
> fs/reiser4/sys_reiser4.c:75: warning: implicit declaration of function `reiser4_pars_init'
> fs/reiser4/sys_reiser4.c:75: warning: assignment makes pointer from integer without a cast
> fs/reiser4/sys_reiser4.c:80: error: dereferencing pointer to incomplete type
> fs/reiser4/sys_reiser4.c:82: warning: implicit declaration of function `yyparse'
> fs/reiser4/sys_reiser4.c:83: warning: implicit declaration of function `reiser4_pars_free'
> fs/reiser4/sys_reiser4.c:66: warning: unused variable `Gencode'
> fs/reiser4/sys_reiser4.c: At top level:
> fs/reiser4/parser/parser.h:333: warning: `Fistmsg' defined but not used
> fs/reiser4/parser/parser.h:342: warning: `typesOfCommand' defined but not used
> fs/reiser4/parser/parser.h:354: warning: `Code' defined but not used
> make[2]: *** [fs/reiser4/sys_reiser4.o] Error 1
> make[1]: *** [fs/reiser4] Error 2
> make: *** [fs] Error 2
> [steven@spc1 linux-2.6.0-test4-r4]$ grep REISER4 .config
> CONFIG_REISER4_FS=y
> CONFIG_REISER4_FS_SYSCALL=y
> CONFIG_REISER4_LARGE_KEY=y
> # CONFIG_REISER4_CHECK is not set
> CONFIG_REISER4_USE_EFLUSH=y
> # CONFIG_REISER4_BADBLOCKS is not set
> 
> 

-- 
Alex.

Re: reiser4 snapshot for August 26th.

[Steven Cole]

On Tue, 2003-08-26 at 12:20, Steven Cole wrote:
> On Tue, 2003-08-26 at 04:22, Oleg Drokin wrote:
> > Hello!
> > 
> >    I have just released another reiser4 snapshot that I hope all interested
> >    parties will try. It is released against 2.6.0-test4.
> >    You can find it at http://namesys.com/snapshots/2003.08.26
> >    I include release notes below.
> > 
> > Reiser4 snapshot for 2003.08.26
> > 
> 
> I got this error while attempting to compile with reiser4.
> Snippet from .config follows.
> 
> Steven
> 
>   CC      fs/reiser4/plugin/file/tail_conversion.o
>   CC      fs/reiser4/sys_reiser4.o
> fs/reiser4/sys_reiser4.c:54:32: parser/parser.code.c: No such file or directory
[snipped]
> [steven@spc1 linux-2.6.0-test4-r4]$ grep REISER4 .config
> CONFIG_REISER4_FS=y
> CONFIG_REISER4_FS_SYSCALL=y

I should have read this more carefully :(

config REISER4_FS_SYSCALL
        bool "Enable reiser4 system call"
        depends on REISER4_FS
        default n
        ---help---
      Adds sys_reiser4() syscall.
      This code is not in good shape yet and may not compile and stuff like that.

Without REISER4_FS_SYSCALL, -test4 with reiser4 compiles fine.  Sorry about the noise.

Steven

Re: reiser4 snapshot for August 26th.

[Oleg Drokin]

Hello!

On Tue, Aug 26, 2003 at 12:20:38PM -0600, Steven Cole wrote:
> >    I have just released another reiser4 snapshot that I hope all interested
> >    parties will try. It is released against 2.6.0-test4.
> >    You can find it at http://namesys.com/snapshots/2003.08.26
> >    I include release notes below.
> > Reiser4 snapshot for 2003.08.26
> I got this error while attempting to compile with reiser4.
> Snippet from .config follows.
> [steven@spc1 linux-2.6.0-test4-r4]$ grep REISER4 .config
> CONFIG_REISER4_FS=y
> CONFIG_REISER4_FS_SYSCALL=y

Do not compile sys reiser4 support. It is not yet ready.
(hm, probably I need to hide that option for next snapshot)


Bye,
    Oleg

Re: reiser4 snapshot for August 26th.

[Alex Zarochentsev]

On Tue, Aug 26, 2003 at 10:41:45PM +0400, Hans Reiser wrote:
> Mr. Demidov, if you put code that does not compile into our tree you 
> need to make the config option for it be invisible.

There is such an option already, CONFIG_REISER4_FS_SYSCALL, 
seems it is off by default.

> 
> Yes?
> 
> Steven, try turning off the sys_reiser4 related code.
> 
> Nikita, if Demidov is not workingtoday (I notice the lack of timesheet 
> commits recently), take care of this for him.
> 
> Hans
> 
> Steven Cole wrote:
> 
> >On Tue, 2003-08-26 at 04:22, Oleg Drokin wrote:
> > 
> >
> >>Hello!
> >>
> >>  I have just released another reiser4 snapshot that I hope all interested
> >>  parties will try. It is released against 2.6.0-test4.
> >>  You can find it at http://namesys.com/snapshots/2003.08.26
> >>  I include release notes below.
> >>
> >>Reiser4 snapshot for 2003.08.26
> >>
> >>   
> >>
> >
> >I got this error while attempting to compile with reiser4.
> >Snippet from .config follows.
> >
> >Steven
> >
> > CC      fs/reiser4/plugin/file/tail_conversion.o
> > CC      fs/reiser4/sys_reiser4.o
> >fs/reiser4/sys_reiser4.c:54:32: parser/parser.code.c: No such file or 
> >directory
> >fs/reiser4/sys_reiser4.c: In function `sys_reiser4':
> >fs/reiser4/sys_reiser4.c:75: warning: implicit declaration of function 
> >`reiser4_pars_init'
> >fs/reiser4/sys_reiser4.c:75: warning: assignment makes pointer from 
> >integer without a cast
> >fs/reiser4/sys_reiser4.c:80: error: dereferencing pointer to incomplete 
> >type
> >fs/reiser4/sys_reiser4.c:82: warning: implicit declaration of function 
> >`yyparse'
> >fs/reiser4/sys_reiser4.c:83: warning: implicit declaration of function 
> >`reiser4_pars_free'
> >fs/reiser4/sys_reiser4.c:66: warning: unused variable `Gencode'
> >fs/reiser4/sys_reiser4.c: At top level:
> >fs/reiser4/parser/parser.h:333: warning: `Fistmsg' defined but not used
> >fs/reiser4/parser/parser.h:342: warning: `typesOfCommand' defined but not 
> >used
> >fs/reiser4/parser/parser.h:354: warning: `Code' defined but not used
> >make[2]: *** [fs/reiser4/sys_reiser4.o] Error 1
> >make[1]: *** [fs/reiser4] Error 2
> >make: *** [fs] Error 2
> >[steven@spc1 linux-2.6.0-test4-r4]$ grep REISER4 .config
> >CONFIG_REISER4_FS=y
> >CONFIG_REISER4_FS_SYSCALL=y
> >CONFIG_REISER4_LARGE_KEY=y
> ># CONFIG_REISER4_CHECK is not set
> >CONFIG_REISER4_USE_EFLUSH=y
> ># CONFIG_REISER4_BADBLOCKS is not set
> >
> >
> >
> >
> > 
> >
> 
> 
> -- 
> Hans
> 
> 

-- 
Alex.

Re: reiser4 snapshot for August 26th.

[Hans Reiser]

Mr. Demidov, if you put code that does not compile into our tree you 
need to make the config option for it be invisible.

Yes?

Steven, try turning off the sys_reiser4 related code.

Nikita, if Demidov is not workingtoday (I notice the lack of timesheet 
commits recently), take care of this for him.

Hans

Steven Cole wrote:

>On Tue, 2003-08-26 at 04:22, Oleg Drokin wrote:
>  
>
>>Hello!
>>
>>   I have just released another reiser4 snapshot that I hope all interested
>>   parties will try. It is released against 2.6.0-test4.
>>   You can find it at http://namesys.com/snapshots/2003.08.26
>>   I include release notes below.
>>
>>Reiser4 snapshot for 2003.08.26
>>
>>    
>>
>
>I got this error while attempting to compile with reiser4.
>Snippet from .config follows.
>
>Steven
>
>  CC      fs/reiser4/plugin/file/tail_conversion.o
>  CC      fs/reiser4/sys_reiser4.o
>fs/reiser4/sys_reiser4.c:54:32: parser/parser.code.c: No such file or directory
>fs/reiser4/sys_reiser4.c: In function `sys_reiser4':
>fs/reiser4/sys_reiser4.c:75: warning: implicit declaration of function `reiser4_pars_init'
>fs/reiser4/sys_reiser4.c:75: warning: assignment makes pointer from integer without a cast
>fs/reiser4/sys_reiser4.c:80: error: dereferencing pointer to incomplete type
>fs/reiser4/sys_reiser4.c:82: warning: implicit declaration of function `yyparse'
>fs/reiser4/sys_reiser4.c:83: warning: implicit declaration of function `reiser4_pars_free'
>fs/reiser4/sys_reiser4.c:66: warning: unused variable `Gencode'
>fs/reiser4/sys_reiser4.c: At top level:
>fs/reiser4/parser/parser.h:333: warning: `Fistmsg' defined but not used
>fs/reiser4/parser/parser.h:342: warning: `typesOfCommand' defined but not used
>fs/reiser4/parser/parser.h:354: warning: `Code' defined but not used
>make[2]: *** [fs/reiser4/sys_reiser4.o] Error 1
>make[1]: *** [fs/reiser4] Error 2
>make: *** [fs] Error 2
>[steven@spc1 linux-2.6.0-test4-r4]$ grep REISER4 .config
>CONFIG_REISER4_FS=y
>CONFIG_REISER4_FS_SYSCALL=y
>CONFIG_REISER4_LARGE_KEY=y
># CONFIG_REISER4_CHECK is not set
>CONFIG_REISER4_USE_EFLUSH=y
># CONFIG_REISER4_BADBLOCKS is not set
>
>
>
>
>  
>


-- 
Hans

Re: reiser4 snapshot for August 26th.

[Steven Cole]

On Tue, 2003-08-26 at 12:41, Alex Zarochentsev wrote:
> On Tue, Aug 26, 2003 at 10:41:45PM +0400, Hans Reiser wrote:
> > Mr. Demidov, if you put code that does not compile into our tree you 
> > need to make the config option for it be invisible.
> 
> There is such an option already, CONFIG_REISER4_FS_SYSCALL, 
> seems it is off by default.

Yes, but I the simple minded user that I am turned it on without reading
the Kconfig help carefully.  Now, it's off, and it compiles.

But, now for more interesting stuff:

[root@spc1 steven]# cd /
[root@spc1 /]# mkdir share_r4
[root@spc1 /]# mount -t reiser4 /dev/hda11 /share_r4
[root@spc1 /]# df -T
Filesystem    Type   1K-blocks      Used Available Use% Mounted on
/dev/hda1     ext3      241116     89449    139219  40% /
/dev/hda9     ext3    20556656  16526188   4030468  81% /home
none         tmpfs      126784         0    126784   0% /dev/shm
/dev/hda8     ext3      241116      4711    223957   3% /tmp
/dev/hda6     ext3     3012204   2507596    351592  88% /usr
/dev/hda7     ext3      489992     70721    393971  16% /var
df: `/share_r4': Value too large for defined data type

I have recently run mkfs.reiser4 on /dev/hda11 with no options.
The reiser4progs version is 0.4.12.

I made a local clone of the 2.6-test bk tree on the new reiser4
file system and that worked OK.

I then did a "time bk -r check -acv", twice for both reiser4 and ext3.
Here are the results for the second run for each (I neglected to
preserve the results for the initial bk -r check -acv):

Reiser4:
real    1m27.774s
user    0m33.685s
sys     0m16.059s

Ext3:
real    2m55.179s
user    0m32.752s
sys     0m5.835s

Nice work.  I'll try to break Reiser4 now.

Steven

Re: reiser4 snapshot for August 26th.

[Hans Reiser]

Alex Zarochentsev wrote:

>On Tue, Aug 26, 2003 at 10:41:45PM +0400, Hans Reiser wrote:
>  
>
>>Mr. Demidov, if you put code that does not compile into our tree you 
>>need to make the config option for it be invisible.
>>    
>>
>
>There is such an option already, CONFIG_REISER4_FS_SYSCALL, 
>seems it is off by default.
>
>  
>
Off != invisible

-- 
Hans

Re: reiser4 snapshot for August 26th.

[Hans Reiser]

Steven Cole wrote:

>On Tue, 2003-08-26 at 12:20, Steven Cole wrote:
>  
>
>>On Tue, 2003-08-26 at 04:22, Oleg Drokin wrote:
>>    
>>
>>>Hello!
>>>
>>>   I have just released another reiser4 snapshot that I hope all interested
>>>   parties will try. It is released against 2.6.0-test4.
>>>   You can find it at http://namesys.com/snapshots/2003.08.26
>>>   I include release notes below.
>>>
>>>Reiser4 snapshot for 2003.08.26
>>>
>>>      
>>>
>>I got this error while attempting to compile with reiser4.
>>Snippet from .config follows.
>>
>>Steven
>>
>>  CC      fs/reiser4/plugin/file/tail_conversion.o
>>  CC      fs/reiser4/sys_reiser4.o
>>fs/reiser4/sys_reiser4.c:54:32: parser/parser.code.c: No such file or directory
>>    
>>
>[snipped]
>  
>
>>[steven@spc1 linux-2.6.0-test4-r4]$ grep REISER4 .config
>>CONFIG_REISER4_FS=y
>>CONFIG_REISER4_FS_SYSCALL=y
>>    
>>
>
>I should have read this more carefully :(
>
>config REISER4_FS_SYSCALL
>        bool "Enable reiser4 system call"
>        depends on REISER4_FS
>        default n
>        ---help---
>      Adds sys_reiser4() syscall.
>      This code is not in good shape yet and may not compile and stuff like that.
>
>Without REISER4_FS_SYSCALL, -test4 with reiser4 compiles fine.  Sorry about the noise.
>
>Steven
>
>
>
>
>  
>
Users should not be expected to read help text in a case like this.If it 
does not compile, it should not be visible.

-- 
Hans

Re: reiser4 snapshot for August 26th.

[Felipe Alfaro Solana]

On Tue, 2003-08-26 at 20:26, Alex Zarochentsev wrote:

> Disable "reiser4 system call" (CONFIG_REISER4_FS_SYSCALL) support, it is 
> not ready.

[...]
  CC      lib/string.o
lib/string.c:435: warning: conflicting types for built-in function
`bcopy'
  CC      lib/vsprintf.o
  AR      lib/lib.a
  LD      arch/i386/lib/built-in.o
  AS      arch/i386/lib/checksum.o
  CC      arch/i386/lib/dec_and_lock.o
  CC      arch/i386/lib/delay.o
  AS      arch/i386/lib/getuser.o
  CC      arch/i386/lib/memcpy.o
  CC      arch/i386/lib/strstr.o
  CC      arch/i386/lib/usercopy.o
  AR      arch/i386/lib/lib.a
  GEN     .version
  CHK     include/linux/compile.h
  UPD     include/linux/compile.h
  CC      init/version.o
  LD      init/built-in.o
  LD      .tmp_vmlinux1
arch/i386/kernel/built-in.o(.data+0x7c4): In function `sys_call_table':
: undefined reference to `sys_reiser4'
make[2]: *** [.tmp_vmlinux1] Error 1
make[1]: *** [vmlinux] Error 2

[...]
CONFIG_REISER4_FS=m
# CONFIG_REISER4_FS_SYSCALL is not set
# CONFIG_REISER4_LARGE_KEY is not set
# CONFIG_REISER4_CHECK is not set
# CONFIG_REISER4_USE_EFLUSH is not set
# CONFIG_REISER4_BADBLOCKS is not set
# CONFIG_REISERFS_FS is not set
# CONFIG_JFS_FS is not set
[...]

Re: reiser4 snapshot for August 26th.

[Oleg Drokin]

Hello!

On Tue, Aug 26, 2003 at 09:36:07PM +0200, Felipe Alfaro Solana wrote:
> > Disable "reiser4 system call" (CONFIG_REISER4_FS_SYSCALL) support, it is 
> > not ready.
> [...]
> arch/i386/kernel/built-in.o(.data+0x7c4): In function `sys_call_table':
> : undefined reference to `sys_reiser4'
> make[2]: *** [.tmp_vmlinux1] Error 1
> make[1]: *** [vmlinux] Error 2
> [...]
> CONFIG_REISER4_FS=m

Building as module is also not yet supported.

Bye,
    Oleg

Re: reiser4 snapshot for August 26th.

[Steven Cole]

On Tue, 2003-08-26 at 13:43, Oleg Drokin wrote:
> Hello!
> 
> On Tue, Aug 26, 2003 at 09:36:07PM +0200, Felipe Alfaro Solana wrote:
> > > Disable "reiser4 system call" (CONFIG_REISER4_FS_SYSCALL) support, it is 
> > > not ready.
> > [...]
> > arch/i386/kernel/built-in.o(.data+0x7c4): In function `sys_call_table':
> > : undefined reference to `sys_reiser4'
> > make[2]: *** [.tmp_vmlinux1] Error 1
> > make[1]: *** [vmlinux] Error 2
> > [...]
> > CONFIG_REISER4_FS=m
> 
> Building as module is also not yet supported.
> 
Fine, then here's a patch:

--- linux-2.6.0-test4-r4/fs/Kconfig.orig	2003-08-26 13:44:38.165059616 -0600
+++ linux-2.6.0-test4-r4/fs/Kconfig	2003-08-26 13:46:43.672979512 -0600
@@ -203,6 +203,9 @@
 	tristate "Reiser4 (EXPERIMENTAL very fast general purpose filesystem)"
 	depends on EXPERIMENTAL
 	---help---
+	  Building as a module is not yet supported, so don't say 'M'
+          unless you're a developer.
+
 	  Reiser4 is more than twice as fast for both reads and writes as
 	  ReiserFS.  That means it is four times as fast as NTFS by Microsoft.
 	  (Proper benchmarks will appear in a few months at

Meanwhile, reiser4 seems to be working fine and is nice and fast.

I did a "time bk -r co" for the current 2.6 tree, and here
are the results for reiser4 and ext3 on 2.6.0-test4:

Reiser4:
real    1m55.077s
user    0m30.740s
sys     0m36.558s

Ext3:
real    3m48.438s
user    0m26.400s
sys     0m13.205s

Steven

Re: reiser4 snapshot for August 26th.

[Mike Fedyk]

On Tue, Aug 26, 2003 at 11:43:21PM +0400, Oleg Drokin wrote:
> Hello!
> 
> On Tue, Aug 26, 2003 at 09:36:07PM +0200, Felipe Alfaro Solana wrote:
> > > Disable "reiser4 system call" (CONFIG_REISER4_FS_SYSCALL) support, it is 
> > > not ready.
> > [...]
> > arch/i386/kernel/built-in.o(.data+0x7c4): In function `sys_call_table':
> > : undefined reference to `sys_reiser4'
> > make[2]: *** [.tmp_vmlinux1] Error 1
> > make[1]: *** [vmlinux] Error 2
> > [...]
> > CONFIG_REISER4_FS=m
> 
> Building as module is also not yet supported.
> 

To do:

remove all options in build system that don't compile.
 o module
 o syscall
 o etc...

how to log reiser and raid0 crash? 2.6.0-t4

[Resident Boxholder]

2.6.0-test4 amd xp 3000+ msi mbo nforce2  four Maxtor 60G 8mbcache raid0

I cause a lock up by doing a cp -aR /usr/src /mnt/usr which moves data 
larger
than total hard buffer cache, to raid0 reiserfs or ext2 ( NOT reiser4!) 
Copy ops
smaller than buffer cache(8mb x 4 = 32mb) don't fail. Nothing fails on a 
single
drive, compiles or copies, just copy to a mounted raid0 device. What 
should I
try, test, or dump?

No irq error storm. No cd drives installed. Smaller copy ops work. Turning
swap off first slows things down enough to work, but swap itself is probably
OK. I have bios turn apic off, then linux turns it on, which is good 
until the
turn apic off before turn apic on patch gets into test5 or whatever.

hdparm sets all four drives the same, udma6 but have tried down to udma4
and pio4 and dma turned off, unmask on or off.

If two drives are on the mboard controller and two on a promise pci card,
does /proc/ide/amd74xx refer to the two drives on the motherboard only?
It seems to mention four drives but the two slow ones might just be a
ref to unoccupied slave drive positions.

I'm wondering what to send in. Maybe I could send a log from successful
copy with swap off, showing reiser logging, and config, in case a stress
condition or misconfig shows up even when catastrophic failure doesn't
occur. With swap on the fail is sudden and no error logging is coming
through.

I could incrementally copy /usr/src to one raid, then do a copy from that
raid to another raid. All that would do is test copying from one balanced
set of four drives/partitions to another balanced set, versus copying from
one drive's /usr/src to that and three other drives' raid set, which is
unbalanced, dragging on one drive.

-Bob

Re: reiser4 snapshot for August 26th.

[Mike Fedyk]

On Tue, Aug 26, 2003 at 01:51:22PM -0600, Steven Cole wrote:
> I did a "time bk -r co" for the current 2.6 tree, and here
> are the results for reiser4 and ext3 on 2.6.0-test4:
> 
> Reiser4:
> real    1m55.077s
> user    0m30.740s
> sys     0m36.558s
> 
> Ext3:
> real    3m48.438s
> user    0m26.400s
> sys     0m13.205s
> 

Can you try ext3 with -o data=writeback, as well as xfs & reiser3?

Thanks

Re: reiser4 snapshot for August 26th.

[Steven Cole]

On Tue, 2003-08-26 at 14:05, Mike Fedyk wrote:
> On Tue, Aug 26, 2003 at 01:51:22PM -0600, Steven Cole wrote:
> > I did a "time bk -r co" for the current 2.6 tree, and here
> > are the results for reiser4 and ext3 on 2.6.0-test4:
> > 
> > Reiser4:
> > real    1m55.077s
> > user    0m30.740s
> > sys     0m36.558s
> > 
> > Ext3:
> > real    3m48.438s
> > user    0m26.400s
> > sys     0m13.205s
> > 
> 
> Can you try ext3 with -o data=writeback, as well as xfs & reiser3?

[root@spc1 /]# umount /dev/hda9
[root@spc1 /]# mount -t ext3 -o data=writeback /dev/hda9 /home
[root@spc1 /]# mount -t reiserfs /dev/hda10 /share_r
[root@spc1 /]# mount -t xfs /dev/hda12 /share_x

[root@spc1 /]# df -T
Filesystem    Type   1K-blocks      Used Available Use% Mounted on
/dev/hda1     ext3      241116     89449    139219  40% /
none         tmpfs      126784         0    126784   0% /dev/shm
/dev/hda8     ext3      241116      4711    223957   3% /tmp
/dev/hda6     ext3     3012204   2507596    351592  88% /usr
/dev/hda7     ext3      489992     70724    393968  16% /var
df: `/share_r4': Value too large for defined data type
/dev/hda9     ext3    20556656  16526268   4030388  81% /home
/dev/hda10
          reiserfs     4112476   1911220   2201256  47% /share_r
/dev/hda12     xfs     4991380    990884   4000496  20% /share_x

Yes, I can do that.  Results in a little while.

BTW, this is RedHat Severn, so df --version gives
[steven@spc1 /]$ df --version
df (coreutils) 5.0

Steven

Re: reiser4 snapshot for August 26th.

[Steven Cole]

On Tue, 2003-08-26 at 14:26, Mike Fedyk wrote:
> On Tue, Aug 26, 2003 at 02:13:51PM -0600, Steven Cole wrote:
> > On Tue, 2003-08-26 at 14:05, Mike Fedyk wrote:
> > > Can you try ext3 with -o data=writeback, as well as xfs & reiser3?
> > 
> > [root@spc1 /]# umount /dev/hda9
> > [root@spc1 /]# mount -t ext3 -o data=writeback /dev/hda9 /home
> > [root@spc1 /]# mount -t reiserfs /dev/hda10 /share_r
> > [root@spc1 /]# mount -t xfs /dev/hda12 /share_x
> > 
> 
> Please use the same partition for all filesystem tests, otherwise you will
> be showing results that need to be adjusted for inner-spindle disk speed.

Good point.  That will take a little more time, but at least the results
will be more meaningful.  Thanks.

Steven

Re: reiser4 snapshot for August 26th.

[Mike Fedyk]

On Tue, Aug 26, 2003 at 02:13:51PM -0600, Steven Cole wrote:
> On Tue, 2003-08-26 at 14:05, Mike Fedyk wrote:
> > Can you try ext3 with -o data=writeback, as well as xfs & reiser3?
> 
> [root@spc1 /]# umount /dev/hda9
> [root@spc1 /]# mount -t ext3 -o data=writeback /dev/hda9 /home
> [root@spc1 /]# mount -t reiserfs /dev/hda10 /share_r
> [root@spc1 /]# mount -t xfs /dev/hda12 /share_x
> 

Please use the same partition for all filesystem tests, otherwise you will
be showing results that need to be adjusted for inner-spindle disk speed.

Re: reiser4 snapshot for August 26th.

[Hans Reiser]

Steven Cole wrote:

>On Tue, 2003-08-26 at 13:43, Oleg Drokin wrote:
>  
>
>>Hello!
>>
>>On Tue, Aug 26, 2003 at 09:36:07PM +0200, Felipe Alfaro Solana wrote:
>>    
>>
>>>>Disable "reiser4 system call" (CONFIG_REISER4_FS_SYSCALL) support, it is 
>>>>not ready.
>>>>        
>>>>
>>>[...]
>>>arch/i386/kernel/built-in.o(.data+0x7c4): In function `sys_call_table':
>>>: undefined reference to `sys_reiser4'
>>>make[2]: *** [.tmp_vmlinux1] Error 1
>>>make[1]: *** [vmlinux] Error 2
>>>[...]
>>>CONFIG_REISER4_FS=m
>>>      
>>>
>>Building as module is also not yet supported.
>>
>>    
>>
>Fine, then here's a patch:
>
>--- linux-2.6.0-test4-r4/fs/Kconfig.orig	2003-08-26 13:44:38.165059616 -0600
>+++ linux-2.6.0-test4-r4/fs/Kconfig	2003-08-26 13:46:43.672979512 -0600
>@@ -203,6 +203,9 @@
> 	tristate "Reiser4 (EXPERIMENTAL very fast general purpose filesystem)"
> 	depends on EXPERIMENTAL
> 	---help---
>+	  Building as a module is not yet supported, so don't say 'M'
>+          unless you're a developer.
>+
> 	  Reiser4 is more than twice as fast for both reads and writes as
> 	  ReiserFS.  That means it is four times as fast as NTFS by Microsoft.
> 	  (Proper benchmarks will appear in a few months at
>
>Meanwhile, reiser4 seems to be working fine and is nice and fast.
>
>I did a "time bk -r co" for the current 2.6 tree, and here
>are the results for reiser4 and ext3 on 2.6.0-test4:
>
>Reiser4:
>real    1m55.077s
>user    0m30.740s
>sys     0m36.558s
>
>Ext3:
>real    3m48.438s
>user    0m26.400s
>sys     0m13.205s
>
>Steven
>
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at  http://www.tux.org/lkml/
>
>
>  
>
Better to disable it entirely.  Features too broken to compile should 
not be warned of, they should be invisible and not selectable in the 
menu.  Thanks Steven and Mike.

-- 
Hans

Re: reiser4 snapshot for August 26th.

[Hans Reiser]

Mike Fedyk wrote:

>On Tue, Aug 26, 2003 at 02:13:51PM -0600, Steven Cole wrote:
>  
>
>>On Tue, 2003-08-26 at 14:05, Mike Fedyk wrote:
>>    
>>
>>>Can you try ext3 with -o data=writeback, as well as xfs & reiser3?
>>>      
>>>
>>[root@spc1 /]# umount /dev/hda9
>>[root@spc1 /]# mount -t ext3 -o data=writeback /dev/hda9 /home
>>[root@spc1 /]# mount -t reiserfs /dev/hda10 /share_r
>>[root@spc1 /]# mount -t xfs /dev/hda12 /share_x
>>
>>    
>>
>
>Please use the same partition for all filesystem tests, otherwise you will
>be showing results that need to be adjusted for inner-spindle disk speed.
>
>
>  
>
Oh yes, Mike is right.

-- 
Hans

Re: reiser4 snapshot for August 26th.

[Diego Calleja García]

[-- Attachment #1: Type: text/plain, Size: 2609 bytes --]

El Tue, 26 Aug 2003 14:22:33 +0400 Oleg Drokin <green@namesys.com> escribió:

> Reiser4 snapshot for 2003.08.26

I got some errors running tiobench (see end of the message) They say something
about ext3 but reiser4 is on the backtrace.

setup: root fs on /; reiser4 on /mnt; running tiobench on /mnt
machine is dual p3 (800 mhz) on ide disk. Config attached

(Also, i wasn't able to run reiser4 as root fs...i got "flushing like mad blah
nikita-something" messages in 3-5s periods.)

btw, I suppose this feature will be removed if/when reiser4 is merged?:
config REISER4_FS_SYSCALL
        bool "Enable reiser4 system call"


dmesg errors:
(fs/ext3/inode.c, 2728): ext3_write_inode: called recursively, non-PF_MEMALLOC!
Call Trace:
 [<c018c715>] write_inode+0x45/0x50
 [<c018c9af>] __sync_single_inode+0x28f/0x310
 [<c018cd00>] generic_sync_sb_inodes+0x1c0/0x2e0
 [<c018cf0c>] writeback_inodes+0xac/0x1d0
 [<c014962c>] balance_dirty_pages+0xbc/0x180
 [<c01cf421>] reiser4_exit_context+0x51/0x60
 [<c01ea9e9>] reiser4_write+0x79/0xb0
 [<c0165e7a>] vfs_write+0xaa/0x130
 [<c0165f9f>] sys_write+0x3f/0x60
 [<c0109b2f>] syscall_call+0x7/0xb

(fs/ext3/inode.c, 2728): ext3_write_inode: called recursively, non-PF_MEMALLOC!
Call Trace:
 [<c018c715>] write_inode+0x45/0x50
 [<c018c9af>] __sync_single_inode+0x28f/0x310
 [<c018cd00>] generic_sync_sb_inodes+0x1c0/0x2e0
 [<c018cf0c>] writeback_inodes+0xac/0x1d0
 [<c014962c>] balance_dirty_pages+0xbc/0x180
 [<c01cf421>] reiser4_exit_context+0x51/0x60
 [<c01ea9e9>] reiser4_write+0x79/0xb0

(fs/ext3/inode.c, 2728): ext3_write_inode: called recursively, non-PF_MEMALLOC!
Call Trace:
 [<c018c715>] write_inode+0x45/0x50
 [<c018c9af>] __sync_single_inode+0x28f/0x310
 [<c018cd00>] generic_sync_sb_inodes+0x1c0/0x2e0
 [<c018cf0c>] writeback_inodes+0xac/0x1d0
 [<c014962c>] balance_dirty_pages+0xbc/0x180
 [<c01cf421>] reiser4_exit_context+0x51/0x60
 [<c01ea9e9>] reiser4_write+0x79/0xb0
 [<c0165e7a>] vfs_write+0xaa/0x130
 [<c0165f9f>] sys_write+0x3f/0x60
 [<c0109b2f>] syscall_call+0x7/0xb

(fs/ext3/inode.c, 2728): ext3_write_inode: called recursively, non-PF_MEMALLOC!
Call Trace:
 [<c018c715>] write_inode+0x45/0x50
 [<c018c9af>] __sync_single_inode+0x28f/0x310
 [<c018cd00>] generic_sync_sb_inodes+0x1c0/0x2e0
 [<c018cf0c>] writeback_inodes+0xac/0x1d0
 [<c014962c>] balance_dirty_pages+0xbc/0x180
 [<c01cf421>] reiser4_exit_context+0x51/0x60
 [<c01ea9e9>] reiser4_write+0x79/0xb0
 [<c0165e7a>] vfs_write+0xaa/0x130
 [<c0165f9f>] sys_write+0x3f/0x60
 [<c0109b2f>] syscall_call+0x7/0xb

(and so on)

[-- Attachment #2: .config --]
[-- Type: application/octet-stream, Size: 21869 bytes --]

#
# Automatically generated make config: don't edit
#
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_UID16=y
CONFIG_GENERIC_ISA_DMA=y

#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
CONFIG_BROKEN=y

#
# General setup
#
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_BSD_PROCESS_ACCT=y
CONFIG_SYSCTL=y
CONFIG_LOG_BUF_SHIFT=15
# CONFIG_IKCONFIG is not set
# CONFIG_EMBEDDED is not set
CONFIG_KALLSYMS=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y

#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
CONFIG_MODULE_FORCE_UNLOAD=y
CONFIG_OBSOLETE_MODPARM=y
CONFIG_MODVERSIONS=y
CONFIG_KMOD=y

#
# Processor type and features
#
CONFIG_X86_PC=y
# CONFIG_X86_VOYAGER is not set
# CONFIG_X86_NUMAQ is not set
# CONFIG_X86_SUMMIT is not set
# CONFIG_X86_BIGSMP is not set
# CONFIG_X86_VISWS is not set
# CONFIG_X86_GENERICARCH is not set
# CONFIG_X86_ES7000 is not set
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_MPENTIUMII is not set
CONFIG_MPENTIUMIII=y
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
# CONFIG_MK8 is not set
# CONFIG_MELAN is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MCYRIXIII is not set
# CONFIG_MVIAC3_2 is not set
# CONFIG_X86_GENERIC is not set
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_L1_CACHE_SHIFT=5
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_HUGETLB_PAGE=y
CONFIG_SMP=y
CONFIG_NR_CPUS=2
CONFIG_PREEMPT=y
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
CONFIG_X86_TSC=y
CONFIG_X86_MCE=y
# CONFIG_X86_MCE_NONFATAL is not set
# CONFIG_X86_MCE_P4THERMAL is not set
# CONFIG_TOSHIBA is not set
# CONFIG_I8K is not set
CONFIG_MICROCODE=y
CONFIG_X86_MSR=y
CONFIG_X86_CPUID=y
# CONFIG_EDD is not set
CONFIG_NOHIGHMEM=y
# CONFIG_HIGHMEM4G is not set
# CONFIG_HIGHMEM64G is not set
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
CONFIG_HAVE_DEC_LOCK=y

#
# Power management options (ACPI, APM)
#
# CONFIG_PM is not set

#
# ACPI (Advanced Configuration and Power Interface) Support
#
CONFIG_ACPI_HT=y
# CONFIG_ACPI is not set
CONFIG_ACPI_BOOT=y

#
# CPU Frequency scaling
#
# CONFIG_CPU_FREQ is not set

#
# Bus options (PCI, PCMCIA, EISA, MCA, ISA)
#
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GODIRECT is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
# CONFIG_PCI_LEGACY_PROC is not set
# CONFIG_PCI_NAMES is not set
# CONFIG_ISA is not set
# CONFIG_MCA is not set
# CONFIG_SCx200 is not set
# CONFIG_HOTPLUG is not set

#
# Executable file formats
#
CONFIG_KCORE_ELF=y
# CONFIG_KCORE_AOUT is not set
CONFIG_BINFMT_ELF=y
# CONFIG_BINFMT_AOUT is not set
# CONFIG_BINFMT_MISC is not set

#
# Generic Driver Options
#

#
# Memory Technology Devices (MTD)
#
# CONFIG_MTD is not set

#
# Parallel port support
#
CONFIG_PARPORT=y
CONFIG_PARPORT_PC=y
CONFIG_PARPORT_PC_CML1=y
# CONFIG_PARPORT_SERIAL is not set
# CONFIG_PARPORT_PC_FIFO is not set
# CONFIG_PARPORT_PC_SUPERIO is not set
# CONFIG_PARPORT_OTHER is not set
CONFIG_PARPORT_1284=y

#
# Plug and Play support
#
CONFIG_PNP=y
CONFIG_PNP_DEBUG=y

#
# Protocols
#
# CONFIG_ISAPNP is not set
CONFIG_PNPBIOS=y

#
# Block devices
#
CONFIG_BLK_DEV_FD=m
# CONFIG_PARIDE is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
CONFIG_BLK_DEV_LOOP=m
# CONFIG_BLK_DEV_CRYPTOLOOP is not set
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_RAM is not set
# CONFIG_BLK_DEV_INITRD is not set
# CONFIG_LBD is not set

#
# ATA/ATAPI/MFM/RLL support
#
CONFIG_IDE=y
CONFIG_BLK_DEV_IDE=y

#
# Please see Documentation/ide.txt for help/info on IDE drives
#
# CONFIG_BLK_DEV_HD_IDE is not set
CONFIG_BLK_DEV_IDEDISK=y
# CONFIG_IDEDISK_MULTI_MODE is not set
# CONFIG_IDEDISK_STROKE is not set
CONFIG_BLK_DEV_IDECD=m
# CONFIG_BLK_DEV_IDETAPE is not set
# CONFIG_BLK_DEV_IDEFLOPPY is not set
# CONFIG_IDE_TASK_IOCTL is not set
CONFIG_IDE_TASKFILE_IO=y

#
# IDE chipset support/bugfixes
#
# CONFIG_BLK_DEV_CMD640 is not set
# CONFIG_BLK_DEV_IDEPNP is not set
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
# CONFIG_BLK_DEV_OFFBOARD is not set
CONFIG_BLK_DEV_GENERIC=y
# CONFIG_BLK_DEV_OPTI621 is not set
# CONFIG_BLK_DEV_RZ1000 is not set
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_IDE_TCQ is not set
# CONFIG_BLK_DEV_IDEDMA_FORCED is not set
CONFIG_IDEDMA_PCI_AUTO=y
# CONFIG_IDEDMA_ONLYDISK is not set
CONFIG_IDEDMA_PCI_WIP=y
# CONFIG_IDEDMA_NEW_DRIVE_LISTINGS is not set
CONFIG_BLK_DEV_ADMA=y
# CONFIG_BLK_DEV_AEC62XX is not set
# CONFIG_BLK_DEV_ALI15X3 is not set
# CONFIG_BLK_DEV_AMD74XX is not set
# CONFIG_BLK_DEV_CMD64X is not set
# CONFIG_BLK_DEV_TRIFLEX is not set
# CONFIG_BLK_DEV_CY82C693 is not set
# CONFIG_BLK_DEV_CS5520 is not set
# CONFIG_BLK_DEV_CS5530 is not set
# CONFIG_BLK_DEV_HPT34X is not set
# CONFIG_BLK_DEV_HPT366 is not set
# CONFIG_BLK_DEV_SC1200 is not set
# CONFIG_BLK_DEV_PIIX is not set
# CONFIG_BLK_DEV_NS87415 is not set
# CONFIG_BLK_DEV_PDC202XX_OLD is not set
# CONFIG_BLK_DEV_PDC202XX_NEW is not set
# CONFIG_BLK_DEV_SVWKS is not set
# CONFIG_BLK_DEV_SIIMAGE is not set
# CONFIG_BLK_DEV_SIS5513 is not set
# CONFIG_BLK_DEV_SLC90E66 is not set
# CONFIG_BLK_DEV_TRM290 is not set
CONFIG_BLK_DEV_VIA82CXXX=y
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_IVB is not set
CONFIG_IDEDMA_AUTO=y
# CONFIG_DMA_NONPCI is not set
# CONFIG_BLK_DEV_HD is not set

#
# SCSI device support
#
# CONFIG_SCSI is not set

#
# Multi-device support (RAID and LVM)
#
# CONFIG_MD is not set

#
# Fusion MPT device support
#

#
# IEEE 1394 (FireWire) support (EXPERIMENTAL)
#
# CONFIG_IEEE1394 is not set

#
# I2O device support
#
# CONFIG_I2O is not set

#
# Networking support
#
CONFIG_NET=y

#
# Networking options
#
CONFIG_PACKET=m
CONFIG_PACKET_MMAP=y
# CONFIG_NETLINK_DEV is not set
CONFIG_UNIX=y
# CONFIG_NET_KEY is not set
CONFIG_INET=y
# CONFIG_IP_MULTICAST is not set
# CONFIG_IP_ADVANCED_ROUTER is not set
# CONFIG_IP_PNP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_ARPD is not set
CONFIG_INET_ECN=y
CONFIG_SYN_COOKIES=y
# CONFIG_INET_AH is not set
# CONFIG_INET_ESP is not set
# CONFIG_INET_IPCOMP is not set

#
# IP: Virtual Server Configuration
#
# CONFIG_IP_VS is not set
CONFIG_IPV6=y
CONFIG_IPV6_PRIVACY=y
CONFIG_INET6_AH=y
CONFIG_INET6_ESP=y
CONFIG_INET6_IPCOMP=y
# CONFIG_IPV6_TUNNEL is not set
# CONFIG_DECNET is not set
# CONFIG_BRIDGE is not set
CONFIG_NETFILTER=y
# CONFIG_NETFILTER_DEBUG is not set

#
# IP: Netfilter Configuration
#
CONFIG_IP_NF_CONNTRACK=m
CONFIG_IP_NF_FTP=m
CONFIG_IP_NF_IRC=m
# CONFIG_IP_NF_TFTP is not set
# CONFIG_IP_NF_AMANDA is not set
CONFIG_IP_NF_QUEUE=m
CONFIG_IP_NF_IPTABLES=m
CONFIG_IP_NF_MATCH_LIMIT=m
CONFIG_IP_NF_MATCH_MAC=m
CONFIG_IP_NF_MATCH_PKTTYPE=m
CONFIG_IP_NF_MATCH_MARK=m
CONFIG_IP_NF_MATCH_MULTIPORT=m
CONFIG_IP_NF_MATCH_TOS=m
# CONFIG_IP_NF_MATCH_RECENT is not set
CONFIG_IP_NF_MATCH_ECN=m
CONFIG_IP_NF_MATCH_DSCP=m
CONFIG_IP_NF_MATCH_AH_ESP=m
CONFIG_IP_NF_MATCH_LENGTH=m
CONFIG_IP_NF_MATCH_TTL=m
CONFIG_IP_NF_MATCH_TCPMSS=m
CONFIG_IP_NF_MATCH_HELPER=m
CONFIG_IP_NF_MATCH_STATE=m
CONFIG_IP_NF_MATCH_CONNTRACK=m
CONFIG_IP_NF_MATCH_UNCLEAN=m
CONFIG_IP_NF_MATCH_OWNER=m
CONFIG_IP_NF_FILTER=m
CONFIG_IP_NF_TARGET_REJECT=m
CONFIG_IP_NF_TARGET_MIRROR=m
CONFIG_IP_NF_NAT=m
CONFIG_IP_NF_NAT_NEEDED=y
CONFIG_IP_NF_TARGET_MASQUERADE=m
CONFIG_IP_NF_TARGET_REDIRECT=m
# CONFIG_IP_NF_NAT_LOCAL is not set
# CONFIG_IP_NF_NAT_SNMP_BASIC is not set
CONFIG_IP_NF_NAT_IRC=m
CONFIG_IP_NF_NAT_FTP=m
# CONFIG_IP_NF_MANGLE is not set
CONFIG_IP_NF_TARGET_LOG=m
CONFIG_IP_NF_TARGET_ULOG=m
# CONFIG_IP_NF_TARGET_TCPMSS is not set
# CONFIG_IP_NF_ARPTABLES is not set
# CONFIG_IP_NF_COMPAT_IPCHAINS is not set
# CONFIG_IP_NF_COMPAT_IPFWADM is not set

#
# IPv6: Netfilter Configuration
#
# CONFIG_IP6_NF_QUEUE is not set
# CONFIG_IP6_NF_IPTABLES is not set
CONFIG_XFRM=y
# CONFIG_XFRM_USER is not set

#
# SCTP Configuration (EXPERIMENTAL)
#
CONFIG_IPV6_SCTP__=y
# CONFIG_IP_SCTP is not set
# CONFIG_ATM is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_LLC is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_NET_DIVERT is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set
# CONFIG_NET_FASTROUTE is not set
# CONFIG_NET_HW_FLOWCONTROL is not set

#
# QoS and/or fair queueing
#
CONFIG_NET_SCHED=y
CONFIG_NET_SCH_CBQ=y
CONFIG_NET_SCH_HTB=y
CONFIG_NET_SCH_CSZ=y
CONFIG_NET_SCH_PRIO=y
CONFIG_NET_SCH_RED=y
CONFIG_NET_SCH_SFQ=y
CONFIG_NET_SCH_TEQL=y
CONFIG_NET_SCH_TBF=y
CONFIG_NET_SCH_GRED=y
CONFIG_NET_SCH_DSMARK=y
CONFIG_NET_SCH_INGRESS=y
CONFIG_NET_QOS=y
CONFIG_NET_ESTIMATOR=y
CONFIG_NET_CLS=y
CONFIG_NET_CLS_TCINDEX=y
CONFIG_NET_CLS_ROUTE4=y
CONFIG_NET_CLS_ROUTE=y
CONFIG_NET_CLS_FW=y
CONFIG_NET_CLS_U32=y
CONFIG_NET_CLS_RSVP=y
CONFIG_NET_CLS_RSVP6=y
CONFIG_NET_CLS_POLICE=y

#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
CONFIG_NETDEVICES=y

#
# ARCnet devices
#
# CONFIG_ARCNET is not set
# CONFIG_DUMMY is not set
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set
# CONFIG_ETHERTAP is not set
# CONFIG_NET_SB1000 is not set

#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=y
# CONFIG_MII is not set
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNGEM is not set
CONFIG_NET_VENDOR_3COM=y
CONFIG_VORTEX=y
# CONFIG_TYPHOON is not set

#
# Tulip family network device support
#
# CONFIG_NET_TULIP is not set
# CONFIG_HP100 is not set
# CONFIG_NET_PCI is not set

#
# Ethernet (1000 Mbit)
#
# CONFIG_ACENIC is not set
# CONFIG_DL2K is not set
# CONFIG_E1000 is not set
# CONFIG_NS83820 is not set
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not set
# CONFIG_R8169 is not set
# CONFIG_SIS190 is not set
# CONFIG_SK98LIN is not set
# CONFIG_TIGON3 is not set

#
# Ethernet (10000 Mbit)
#
# CONFIG_IXGB is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_PLIP is not set
CONFIG_PPP=m
# CONFIG_PPP_MULTILINK is not set
# CONFIG_PPP_FILTER is not set
CONFIG_PPP_ASYNC=m
# CONFIG_PPP_SYNC_TTY is not set
CONFIG_PPP_DEFLATE=m
CONFIG_PPP_BSDCOMP=m
# CONFIG_PPPOE is not set
# CONFIG_SLIP is not set

#
# Wireless LAN (non-hamradio)
#
# CONFIG_NET_RADIO is not set

#
# Token Ring devices (depends on LLC=y)
#
# CONFIG_RCPCI is not set
# CONFIG_SHAPER is not set

#
# Wan interfaces
#
# CONFIG_WAN is not set

#
# Amateur Radio support
#
# CONFIG_HAMRADIO is not set

#
# IrDA (infrared) support
#
# CONFIG_IRDA is not set

#
# ISDN subsystem
#
# CONFIG_ISDN_BOOL is not set

#
# Telephony Support
#
# CONFIG_PHONE is not set

#
# Input device support
#
CONFIG_INPUT=y

#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
# CONFIG_INPUT_JOYDEV is not set
# CONFIG_INPUT_TSDEV is not set
# CONFIG_INPUT_EVDEV is not set
# CONFIG_INPUT_EVBUG is not set

#
# Input I/O drivers
#
# CONFIG_GAMEPORT is not set
CONFIG_SOUND_GAMEPORT=y
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
CONFIG_SERIO_SERPORT=y
# CONFIG_SERIO_CT82C710 is not set
# CONFIG_SERIO_PARKBD is not set
# CONFIG_SERIO_PCIPS2 is not set

#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_KEYBOARD_NEWTON is not set
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
CONFIG_MOUSE_SERIAL=y
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
CONFIG_INPUT_MISC=y
# CONFIG_INPUT_PCSPKR is not set
# CONFIG_INPUT_UINPUT is not set

#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
# CONFIG_SERIAL_NONSTANDARD is not set

#
# Serial drivers
#
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_CONSOLE=y
# CONFIG_SERIAL_8250_EXTENDED is not set

#
# Non-8250 serial port support
#
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
CONFIG_UNIX98_PTYS=y
CONFIG_UNIX98_PTY_COUNT=256
CONFIG_PRINTER=y
CONFIG_LP_CONSOLE=y
CONFIG_PPDEV=y
# CONFIG_TIPAR is not set

#
# I2C support
#
# CONFIG_I2C is not set

#
# I2C Hardware Sensors Mainboard support
#

#
# I2C Hardware Sensors Chip support
#
# CONFIG_I2C_SENSOR is not set

#
# Mice
#
# CONFIG_BUSMOUSE is not set
# CONFIG_QIC02_TAPE is not set

#
# IPMI
#
# CONFIG_IPMI_HANDLER is not set

#
# Watchdog Cards
#
CONFIG_WATCHDOG=y
# CONFIG_WATCHDOG_NOWAYOUT is not set
# CONFIG_SOFT_WATCHDOG is not set
# CONFIG_WDT is not set
# CONFIG_WDTPCI is not set
# CONFIG_PCWATCHDOG is not set
# CONFIG_ACQUIRE_WDT is not set
# CONFIG_ADVANTECH_WDT is not set
# CONFIG_EUROTECH_WDT is not set
# CONFIG_IB700_WDT is not set
# CONFIG_I810_TCO is not set
# CONFIG_MIXCOMWD is not set
# CONFIG_SCx200_WDT is not set
# CONFIG_60XX_WDT is not set
# CONFIG_W83877F_WDT is not set
# CONFIG_MACHZ_WDT is not set
# CONFIG_SC520_WDT is not set
# CONFIG_AMD7XX_TCO is not set
# CONFIG_ALIM7101_WDT is not set
# CONFIG_SC1200_WDT is not set
# CONFIG_WAFER_WDT is not set
# CONFIG_CPU5_WDT is not set
# CONFIG_HW_RANDOM is not set
# CONFIG_NVRAM is not set
CONFIG_RTC=y
# CONFIG_DTLK is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
# CONFIG_SONYPI is not set

#
# Ftape, the floppy tape device driver
#
# CONFIG_FTAPE is not set
CONFIG_AGP=y
# CONFIG_AGP_ALI is not set
# CONFIG_AGP_ATI is not set
# CONFIG_AGP_AMD is not set
# CONFIG_AGP_AMD_8151 is not set
# CONFIG_AGP_INTEL is not set
# CONFIG_AGP_NVIDIA is not set
# CONFIG_AGP_SIS is not set
# CONFIG_AGP_SWORKS is not set
CONFIG_AGP_VIA=y
CONFIG_DRM=y
CONFIG_DRM_TDFX=m
# CONFIG_DRM_GAMMA is not set
# CONFIG_DRM_R128 is not set
# CONFIG_DRM_RADEON is not set
# CONFIG_DRM_MGA is not set
# CONFIG_MWAVE is not set
# CONFIG_RAW_DRIVER is not set
# CONFIG_HANGCHECK_TIMER is not set

#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set

#
# Digital Video Broadcasting Devices
#
# CONFIG_DVB is not set

#
# File systems
#
# CONFIG_EXT2_FS is not set
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
CONFIG_EXT3_FS_SECURITY=y
CONFIG_JBD=y
CONFIG_JBD_DEBUG=y
CONFIG_FS_MBCACHE=y
CONFIG_REISER4_FS=y
# CONFIG_REISER4_FS_SYSCALL is not set
CONFIG_REISER4_LARGE_KEY=y
# CONFIG_REISER4_CHECK is not set
CONFIG_REISER4_USE_EFLUSH=y
# CONFIG_REISER4_BADBLOCKS is not set
# CONFIG_REISERFS_FS is not set
# CONFIG_JFS_FS is not set
CONFIG_FS_POSIX_ACL=y
# CONFIG_XFS_FS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_ROMFS_FS is not set
# CONFIG_QUOTA is not set
# CONFIG_AUTOFS_FS is not set
# CONFIG_AUTOFS4_FS is not set

#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=m
CONFIG_JOLIET=y
CONFIG_ZISOFS=y
CONFIG_ZISOFS_FS=m
# CONFIG_UDF_FS is not set

#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=m
# CONFIG_MSDOS_FS is not set
CONFIG_VFAT_FS=m
CONFIG_NTFS_FS=m
CONFIG_NTFS_DEBUG=y
# CONFIG_NTFS_RW is not set

#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
# CONFIG_DEVFS_FS is not set
CONFIG_DEVPTS_FS=y
# CONFIG_DEVPTS_FS_XATTR is not set
# CONFIG_TMPFS is not set
# CONFIG_HUGETLBFS is not set
CONFIG_RAMFS=y

#
# Miscellaneous filesystems
#
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
# CONFIG_CRAMFS is not set
# CONFIG_VXFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set

#
# Network File Systems
#
# CONFIG_NFS_FS is not set
# CONFIG_NFSD is not set
# CONFIG_EXPORTFS is not set
# CONFIG_SMB_FS is not set
# CONFIG_CIFS is not set
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set
# CONFIG_INTERMEZZO_FS is not set
# CONFIG_AFS_FS is not set

#
# Partition Types
#
# CONFIG_PARTITION_ADVANCED is not set
CONFIG_MSDOS_PARTITION=y
CONFIG_NLS=y

#
# Native Language Support
#
CONFIG_NLS_DEFAULT="iso8859-15"
# CONFIG_NLS_CODEPAGE_437 is not set
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
CONFIG_NLS_CODEPAGE_850=m
# CONFIG_NLS_CODEPAGE_852 is not set
# CONFIG_NLS_CODEPAGE_855 is not set
# CONFIG_NLS_CODEPAGE_857 is not set
# CONFIG_NLS_CODEPAGE_860 is not set
# CONFIG_NLS_CODEPAGE_861 is not set
# CONFIG_NLS_CODEPAGE_862 is not set
# CONFIG_NLS_CODEPAGE_863 is not set
# CONFIG_NLS_CODEPAGE_864 is not set
# CONFIG_NLS_CODEPAGE_865 is not set
# CONFIG_NLS_CODEPAGE_866 is not set
# CONFIG_NLS_CODEPAGE_869 is not set
# CONFIG_NLS_CODEPAGE_936 is not set
# CONFIG_NLS_CODEPAGE_950 is not set
# CONFIG_NLS_CODEPAGE_932 is not set
# CONFIG_NLS_CODEPAGE_949 is not set
# CONFIG_NLS_CODEPAGE_874 is not set
# CONFIG_NLS_ISO8859_8 is not set
# CONFIG_NLS_CODEPAGE_1250 is not set
# CONFIG_NLS_CODEPAGE_1251 is not set
# CONFIG_NLS_ISO8859_1 is not set
# CONFIG_NLS_ISO8859_2 is not set
# CONFIG_NLS_ISO8859_3 is not set
# CONFIG_NLS_ISO8859_4 is not set
# CONFIG_NLS_ISO8859_5 is not set
# CONFIG_NLS_ISO8859_6 is not set
# CONFIG_NLS_ISO8859_7 is not set
# CONFIG_NLS_ISO8859_9 is not set
# CONFIG_NLS_ISO8859_13 is not set
# CONFIG_NLS_ISO8859_14 is not set
# CONFIG_NLS_ISO8859_15 is not set
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
CONFIG_NLS_UTF8=m

#
# Graphics support
#
# CONFIG_FB is not set
CONFIG_VIDEO_SELECT=y

#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
# CONFIG_MDA_CONSOLE is not set
CONFIG_DUMMY_CONSOLE=y

#
# Sound
#
CONFIG_SOUND=y

#
# Advanced Linux Sound Architecture
#
CONFIG_SND=y
CONFIG_SND_SEQUENCER=y
CONFIG_SND_SEQ_DUMMY=y
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=y
CONFIG_SND_PCM_OSS=y
# CONFIG_SND_SEQUENCER_OSS is not set
CONFIG_SND_RTCTIMER=y
CONFIG_SND_VERBOSE_PRINTK=y
CONFIG_SND_DEBUG=y
CONFIG_SND_DEBUG_MEMORY=y
# CONFIG_SND_DEBUG_DETECT is not set

#
# Generic devices
#
# CONFIG_SND_DUMMY is not set
# CONFIG_SND_VIRMIDI is not set
# CONFIG_SND_MTPAV is not set
# CONFIG_SND_SERIAL_U16550 is not set
# CONFIG_SND_MPU401 is not set

#
# PCI devices
#
# CONFIG_SND_ALI5451 is not set
# CONFIG_SND_AZT3328 is not set
# CONFIG_SND_CS46XX is not set
# CONFIG_SND_CS4281 is not set
# CONFIG_SND_EMU10K1 is not set
# CONFIG_SND_KORG1212 is not set
# CONFIG_SND_NM256 is not set
# CONFIG_SND_RME32 is not set
# CONFIG_SND_RME96 is not set
# CONFIG_SND_RME9652 is not set
# CONFIG_SND_HDSP is not set
# CONFIG_SND_TRIDENT is not set
# CONFIG_SND_YMFPCI is not set
# CONFIG_SND_ALS4000 is not set
# CONFIG_SND_CMIPCI is not set
# CONFIG_SND_ENS1370 is not set
# CONFIG_SND_ENS1371 is not set
# CONFIG_SND_ES1938 is not set
# CONFIG_SND_ES1968 is not set
# CONFIG_SND_MAESTRO3 is not set
# CONFIG_SND_FM801 is not set
# CONFIG_SND_ICE1712 is not set
# CONFIG_SND_ICE1724 is not set
# CONFIG_SND_INTEL8X0 is not set
# CONFIG_SND_SONICVIBES is not set
CONFIG_SND_VIA82XX=y
# CONFIG_SND_VX222 is not set

#
# ALSA USB devices
#
# CONFIG_SND_USB_AUDIO is not set

#
# Open Sound System
#
# CONFIG_SOUND_PRIME is not set

#
# USB support
#
CONFIG_USB=m
CONFIG_USB_DEBUG=y

#
# Miscellaneous USB options
#
CONFIG_USB_DEVICEFS=y
CONFIG_USB_BANDWIDTH=y
CONFIG_USB_DYNAMIC_MINORS=y

#
# USB Host Controller Drivers
#
# CONFIG_USB_EHCI_HCD is not set
# CONFIG_USB_OHCI_HCD is not set
CONFIG_USB_UHCI_HCD=m

#
# USB Device Class drivers
#
# CONFIG_USB_AUDIO is not set
# CONFIG_USB_BLUETOOTH_TTY is not set
# CONFIG_USB_MIDI is not set
# CONFIG_USB_ACM is not set
# CONFIG_USB_PRINTER is not set

#
# SCSI support is needed for USB Storage
#
# CONFIG_USB_STORAGE is not set

#
# USB Human Interface Devices (HID)
#
# CONFIG_USB_HID is not set

#
# USB HID Boot Protocol drivers
#
# CONFIG_USB_KBD is not set
# CONFIG_USB_MOUSE is not set
# CONFIG_USB_AIPTEK is not set
# CONFIG_USB_WACOM is not set
# CONFIG_USB_KBTAB is not set
# CONFIG_USB_POWERMATE is not set
# CONFIG_USB_XPAD is not set

#
# USB Imaging devices
#
# CONFIG_USB_MDC800 is not set
# CONFIG_USB_SCANNER is not set

#
# USB Multimedia devices
#
# CONFIG_USB_DABUSB is not set

#
# Video4Linux support is needed for USB Multimedia device support
#

#
# USB Network adaptors
#
# CONFIG_USB_AX8817X is not set
# CONFIG_USB_CATC is not set
# CONFIG_USB_KAWETH is not set
# CONFIG_USB_PEGASUS is not set
# CONFIG_USB_RTL8150 is not set
# CONFIG_USB_USBNET is not set

#
# USB port drivers
#
# CONFIG_USB_USS720 is not set

#
# USB Serial Converter support
#
# CONFIG_USB_SERIAL is not set

#
# USB Miscellaneous drivers
#
# CONFIG_USB_TIGL is not set
# CONFIG_USB_AUERSWALD is not set
# CONFIG_USB_RIO500 is not set
# CONFIG_USB_BRLVGER is not set
# CONFIG_USB_LCD is not set
# CONFIG_USB_TEST is not set
# CONFIG_USB_GADGET is not set

#
# Bluetooth support
#
# CONFIG_BT is not set

#
# Profiling support
#
CONFIG_PROFILING=y
CONFIG_OPROFILE=m

#
# Kernel hacking
#
CONFIG_DEBUG_KERNEL=y
CONFIG_DEBUG_STACKOVERFLOW=y
CONFIG_DEBUG_SLAB=y
CONFIG_DEBUG_IOVIRT=y
CONFIG_MAGIC_SYSRQ=y
CONFIG_DEBUG_SPINLOCK=y
CONFIG_DEBUG_PAGEALLOC=y
CONFIG_DEBUG_INFO=y
CONFIG_DEBUG_SPINLOCK_SLEEP=y
CONFIG_FRAME_POINTER=y
CONFIG_X86_EXTRA_IRQS=y
CONFIG_X86_FIND_SMP_CONFIG=y
CONFIG_X86_MPPARSE=y

#
# Security options
#
# CONFIG_SECURITY is not set

#
# Cryptographic options
#
CONFIG_CRYPTO=y
CONFIG_CRYPTO_HMAC=y
# CONFIG_CRYPTO_NULL is not set
# CONFIG_CRYPTO_MD4 is not set
CONFIG_CRYPTO_MD5=y
CONFIG_CRYPTO_SHA1=y
# CONFIG_CRYPTO_SHA256 is not set
# CONFIG_CRYPTO_SHA512 is not set
CONFIG_CRYPTO_DES=y
# CONFIG_CRYPTO_BLOWFISH is not set
# CONFIG_CRYPTO_TWOFISH is not set
# CONFIG_CRYPTO_SERPENT is not set
# CONFIG_CRYPTO_AES is not set
# CONFIG_CRYPTO_CAST5 is not set
# CONFIG_CRYPTO_CAST6 is not set
CONFIG_CRYPTO_DEFLATE=y
# CONFIG_CRYPTO_TEST is not set

#
# Library routines
#
# CONFIG_CRC32 is not set
CONFIG_ZLIB_INFLATE=y
CONFIG_ZLIB_DEFLATE=y
CONFIG_X86_SMP=y
CONFIG_X86_HT=y
CONFIG_X86_BIOS_REBOOT=y
CONFIG_X86_TRAMPOLINE=y

Re: how to log reiser and raid0 crash? 2.6.0-t4

[Resident Boxholder]

I had syslog send just *.info to vc/5 and though the *.info messages 
never make
it into syslog file, I started cp -aR /usr/src/kernel-source-2.6.0 /tmp 
with md/2 mounted
to /tmp and saw this *.info on vc/5 and then it locked up.  How about 
those zeros, skip,
assign id anyway?

journal_1037: journal_read_transaction, offset 3623, len 0 mount_id 0
journal_1039: journal_read_trans skipping because 3623 is too old
journal_1299: Setting newest_mount_id to 12

Anything?

-Bob D

Resident Boxholder wrote:

> 2.6.0-test4 amd xp 3000+ msi mbo nforce2  four Maxtor 60G 8mbcache raid0
>
> I cause a lock up by doing a cp -aR /usr/src /mnt/usr which moves data 
> larger
> than total hard buffer cache, to raid0 reiserfs or ext2 ( NOT 
> reiser4!) Copy ops
> smaller than buffer cache(8mb x 4 = 32mb) don't fail. Nothing fails on 
> a single
> drive, compiles or copies, just copy to a mounted raid0 device. What 
> should I
> try, test, or dump?
>
> No irq error storm. No cd drives installed. Smaller copy ops work. 
> Turning
> swap off first slows things down enough to work, but swap itself is 
> probably
> OK. I have bios turn apic off, then linux turns it on, which is good 
> until the
> turn apic off before turn apic on patch gets into test5 or whatever.
>
> hdparm sets all four drives the same, udma6 but have tried down to udma4
> and pio4 and dma turned off, unmask on or off.
>
> If two drives are on the mboard controller and two on a promise pci card,
> does /proc/ide/amd74xx refer to the two drives on the motherboard only?
> It seems to mention four drives but the two slow ones might just be a
> ref to unoccupied slave drive positions.
>
> I'm wondering what to send in. Maybe I could send a log from successful
> copy with swap off, showing reiser logging, and config, in case a stress
> condition or misconfig shows up even when catastrophic failure doesn't
> occur. With swap on the fail is sudden and no error logging is coming
> through.
>
> I could incrementally copy /usr/src to one raid, then do a copy from that
> raid to another raid. All that would do is test copying from one balanced
> set of four drives/partitions to another balanced set, versus copying 
> from
> one drive's /usr/src to that and three other drives' raid set, which is
> unbalanced, dragging on one drive.
>
> -Bob
>
> -
> To unsubscribe from this list: send the line "unsubscribe 
> linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>
>

Re: reiser4 snapshot for August 26th.

[Ian Wienand]

On Tue, Aug 26, 2003 at 02:22:33PM +0400, Oleg Drokin wrote:
> Fixed some bugs. And finally reiser4 should compile on 64bit boxes
> (hm. somebody try it, as I am unable to build any 2.6 kernel for
> ia64).

I built this with IA64 2.6.0-test4, it works but there were lots of
warnings (I can put up a log if you want it).  This was on a dual
processor Itanium 2 box.

First up, I tried a little test to make a few files, but once I had
unmounted the disk I couldn't re-mount it.

--- example testing below ---
bash-2.05b# mkfs.reiser4 /dev/sda5
mkfs.reiser4 0.4.12
Copyright (C) 2001, 2002, 2003 by Hans Reiser, licensing governed by reiser4progs/COPYING.
 
Information: Reiser4 is going to be created on /dev/sda5.
(Yes/No): Yes
Creating reiser4 on /dev/sda5...
mkfs.reiser4(5676): unaligned access to 0x60000000000242f2, ip=0x20000000000f7661
mkfs.reiser4(5676): unaligned access to 0x60000000000242fa, ip=0x20000000000f77a1
mkfs.reiser4(5676): unaligned access to 0x6000000000024302, ip=0x20000000000f78e1
mkfs.reiser4(5676): unaligned access to 0x60000000000242f2, ip=0x20000000000f2671
done
Synchronizing /dev/sda5...done
bash-2.05b# mount -t reiser4 /dev/sda5 /mnt
bash-2.05b# cd /mnt
bash-2.05b# time for i in `seq 1 10000` ; do touch $i ; done
 
real    0m18.577s
user    0m5.910s
sys     0m12.657s

[do ls, all looks ok]

bash-2.05b# umount /mnt
bash-2.05b# mount -t reiser4 /dev/sda5 /mnt
mount: wrong fs type, bad option, bad superblock on /dev/sda5,
       or too many mounted file systems

--- end example testing ---
The console popped up with :

reiser4[mount(15688)]: reiser4_fill_super (fs/reiser4/vfs_ops.c:1229)[nikita-2608]:
WARNING: Wrong magic: 10000 != 62533452

when I tried to mount it.

I repeated this, but this time thought I'd try 'sync' before
unmounting the disk; the sync command just hung and from that point
nothing could seem to access disk, even on different partitions (so
each program became unresponsive as soon as it tried to open a file).

Then I tried the mongo.pl script just for something else, I used the
parameters given in the sample config, i.e.

FSTYPE=reiser4
BYTES=250000000
FILE_SIZE=4096

It just seemed to hang in "PHASE Create" and after, say a minute or
two, made the machine unresponsive in the same way as 'sync' above --
as soon as anything tried to access disk it just hung.

So I retried this, and did a ls in the mounted directory just after I
started mongo to try and poke at what it was up to; ls hung in the
same way but this time I got messages :

 reiser4[ls(30795)]: traverse_tree (fs/reiser4/search.c:488)[nikita-1481]:
WARNING: Too many iterations: 128
 reiser4[ls(30795)]: traverse_tree (fs/reiser4/search.c:488)[nikita-1481]:
WARNING: Too many iterations: 256
 reiser4[ls(30795)]: traverse_tree (fs/reiser4/search.c:488)[nikita-1481]:
WARNING: Too many iterations: 512
 reiser4[ls(30795)]: traverse_tree (fs/reiser4/search.c:488)[nikita-1481]:
WARNING: Too many iterations: 1024
 reiser4[ls(30795)]: traverse_tree (fs/reiser4/search.c:488)[nikita-1481]:
WARNING: Too many iterations: 2048

that just kept climbing ...

I'm happy to help more, but I think a little more targetting debugging
is required.  Could you suggest what would be helpful for me to try?

-i
ianw@gelato.unsw.edu.au
http://www.gelato.unsw.edu.au

Re: reiser4 snapshot for August 26th.

[Yury Umanets]

On Wed, 2003-08-27 at 09:52, Ian Wienand wrote:
> On Tue, Aug 26, 2003 at 02:22:33PM +0400, Oleg Drokin wrote:
> > Fixed some bugs. And finally reiser4 should compile on 64bit boxes
> > (hm. somebody try it, as I am unable to build any 2.6 kernel for
> > ia64).
> 
> I built this with IA64 2.6.0-test4, it works but there were lots of
> warnings (I can put up a log if you want it).  This was on a dual
> processor Itanium 2 box.
> 
> First up, I tried a little test to make a few files, but once I had
> unmounted the disk I couldn't re-mount it.
> 
> --- example testing below ---

> bash-2.05b# mkfs.reiser4 /dev/sda5
> mkfs.reiser4 0.4.12
> Copyright (C) 2001, 2002, 2003 by Hans Reiser, licensing governed by reiser4progs/COPYING.
>  
> Information: Reiser4 is going to be created on /dev/sda5.
> (Yes/No): Yes
> Creating reiser4 on /dev/sda5...
> mkfs.reiser4(5676): unaligned access to 0x60000000000242f2, ip=0x20000000000f7661
> mkfs.reiser4(5676): unaligned access to 0x60000000000242fa, ip=0x20000000000f77a1
> mkfs.reiser4(5676): unaligned access to 0x6000000000024302, ip=0x20000000000f78e1
> mkfs.reiser4(5676): unaligned access to 0x60000000000242f2, ip=0x20000000000f2671
> done
> Synchronizing /dev/sda5...done

I will fix it soon.

Thanks for report.

Regards.

Re: reiser4 snapshot for August 26th.

[Oleg Drokin]

Hello!

On Tue, Aug 26, 2003 at 11:28:44PM +0200, Diego Calleja Garc?a wrote:

> btw, I suppose this feature will be removed if/when reiser4 is merged?:
> config REISER4_FS_SYSCALL
>         bool "Enable reiser4 system call"

No. It will be fixed.

> dmesg errors:
> (fs/ext3/inode.c, 2728): ext3_write_inode: called recursively, non-PF_MEMALLOC!
> Call Trace:
>  [<c018c715>] write_inode+0x45/0x50
>  [<c018c9af>] __sync_single_inode+0x28f/0x310
>  [<c018cd00>] generic_sync_sb_inodes+0x1c0/0x2e0

Hm. Interesting Thank you for the report. We will fix it.

Bye,
    Oleg

Re: how to log reiser and raid0 crash? 2.6.0-t4

[Oleg Drokin]

Hello!

On Tue, Aug 26, 2003 at 03:57:39PM -0400, Resident Boxholder wrote:

> I cause a lock up by doing a cp -aR /usr/src /mnt/usr which moves data 
> larger
> than total hard buffer cache, to raid0 reiserfs or ext2 ( NOT reiser4!) 
> I'm wondering what to send in. Maybe I could send a log from successful
> copy with swap off, showing reiser logging, and config, in case a stress
> condition or misconfig shows up even when catastrophic failure doesn't
> occur. With swap on the fail is sudden and no error logging is coming
> through.

Is there any chance of using sirial console to see if you can capture something on that?

Bye,
    Oleg

Re: reiser4 snapshot for August 26th.

[Felipe Alfaro Solana]

On Wed, 2003-08-27 at 08:03, Yury Umanets wrote:
> >  
> > Information: Reiser4 is going to be created on /dev/sda5.
> > (Yes/No): Yes
> > Creating reiser4 on /dev/sda5...
> > mkfs.reiser4(5676): unaligned access to 0x60000000000242f2, ip=0x20000000000f7661
> > mkfs.reiser4(5676): unaligned access to 0x60000000000242fa, ip=0x20000000000f77a1
> > mkfs.reiser4(5676): unaligned access to 0x6000000000024302, ip=0x20000000000f78e1
> > mkfs.reiser4(5676): unaligned access to 0x60000000000242f2, ip=0x20000000000f2671
> > done
> > Synchronizing /dev/sda5...done
> 
> I will fix it soon.

Will Reiser4 be integrated into 2.6.0-test kernels anytime soon?
This would reduce time between releases and would open up it to a wider
audience for testing

Re: reiser4 snapshot for August 26th.

[Hans Reiser]

Felipe Alfaro Solana wrote:

>On Wed, 2003-08-27 at 08:03, Yury Umanets wrote:
>  
>
>>> 
>>>Information: Reiser4 is going to be created on /dev/sda5.
>>>(Yes/No): Yes
>>>Creating reiser4 on /dev/sda5...
>>>mkfs.reiser4(5676): unaligned access to 0x60000000000242f2, ip=0x20000000000f7661
>>>mkfs.reiser4(5676): unaligned access to 0x60000000000242fa, ip=0x20000000000f77a1
>>>mkfs.reiser4(5676): unaligned access to 0x6000000000024302, ip=0x20000000000f78e1
>>>mkfs.reiser4(5676): unaligned access to 0x60000000000242f2, ip=0x20000000000f2671
>>>done
>>>Synchronizing /dev/sda5...done
>>>      
>>>
>>I will fix it soon.
>>    
>>
>
>Will Reiser4 be integrated into 2.6.0-test kernels anytime soon?
>This would reduce time between releases and would open up it to a wider
>audience for testing
>
>
>
>  
>
This is not a Namesys decision, I encourage you to ask Linus and Andrew 
about it though.  I would like to see it go in as an experimental marked 
filesystem....

-- 
Hans

Re: how to log reiser and raid0 crash? 2.6.0-t4

[Resident Boxholder]

2.6.0-t4 amd 3000+ 1G four maxtor 60G drives on two controllers(mb's and 
promise)

problem isolated to promise card(have to verify the other is error-free 
longer though)

Oleg Drokin wrote:

>Hello!
>
>On Tue, Aug 26, 2003 at 03:57:39PM -0400, Resident Boxholder wrote:
>
>  
>
>>I cause a lock up by doing a cp -aR /usr/src /mnt/usr...
>>    
>>
>
>Is there any chance of using sirial console to see if you can capture something on that?
>
>Bye,
>    Oleg
>
I have a second linux pc and I can google whether to use null or regular 
serial cable,
howto put a console on serial, then log to that, I guess that's all. As 
a bonus I won't
need a kvm switch anymore.

Here's some repeatable "high-level(monkey-level)" info.

I have four drives, two on mboard controller and two on a 133 Promise card.
If I make a four-drive four-partition raid zero md device, I get enough 
lockups
to draw my attention, so then I make two-drive md devices to see which
controller works, if any. Without really flogging it I got ext2 and 
reiserfs on
the mboard's two drives to work for mkfs, fsck, and copy /usr/src/ /tmp
so maybe this is a Promise problem. The mboard controller handles udma6
no problem for that two-drive md.

With only two drives on the promise card forming a raid zero md device,
crashes happen on mkfs and fscks and even though no md's are mounted
on boot, the boot won't happen sometimes after a crash.

I have no errors logging anymore. The only one I got was by switching to
vc/5 and seeing reiserfs info but I don't see that anymore since fixing one
thing, it was because of mdadm and debian config conflict, forget that.
The irq error storm was a false lead as well, no more such errors, no
errors at all logged, since removing cd's and second promise card and
turning usb off and turning apic off in bios and letting linux turn apic on.
ACPI is smooth, no errors, just sudden death.

Things I've tried are no fastrak in promise kernel config, hdparm no dma,
hdparm udma4 instead of udma6. I'll try pio4 pio3 on the promise md
and really flog the mboard-controlled md to verify that there is no
problem except on the promise card. I'm reading what Alan Cox is
saying about "LBA48 pio and udma" so I will try turning dma off
and going down in pio modes.

Swap is working with four drives, so two on the promise card, but with 1G of
ram swap on the promise card may never be used.

-Bob D

Re: reiser4 snapshot for August 26th.

[Alex Zarochentsev]

On Tue, Aug 26, 2003 at 01:14:46PM -0600, Steven Cole wrote:
> On Tue, 2003-08-26 at 12:41, Alex Zarochentsev wrote:
> > On Tue, Aug 26, 2003 at 10:41:45PM +0400, Hans Reiser wrote:
> > > Mr. Demidov, if you put code that does not compile into our tree you 
> > > need to make the config option for it be invisible.
> > 
> > There is such an option already, CONFIG_REISER4_FS_SYSCALL, 
> > seems it is off by default.
> 
> Yes, but I the simple minded user that I am turned it on without reading
> the Kconfig help carefully.  Now, it's off, and it compiles.
> 
> But, now for more interesting stuff:
> 
> [root@spc1 steven]# cd /
> [root@spc1 /]# mkdir share_r4
> [root@spc1 /]# mount -t reiser4 /dev/hda11 /share_r4
> [root@spc1 /]# df -T
> Filesystem    Type   1K-blocks      Used Available Use% Mounted on
> /dev/hda1     ext3      241116     89449    139219  40% /
> /dev/hda9     ext3    20556656  16526188   4030468  81% /home
> none         tmpfs      126784         0    126784   0% /dev/shm
> /dev/hda8     ext3      241116      4711    223957   3% /tmp
> /dev/hda6     ext3     3012204   2507596    351592  88% /usr
> /dev/hda7     ext3      489992     70721    393971  16% /var
> df: `/share_r4': Value too large for defined data type

I can't reproduce that.  Do you see df errors each time you mount just created
reiser4 fs?  Can you provide additional information about your system:
distro, libc which you used?  

My hypothesysis is that libc statfs or df itself want to convert "free inodes"
result parameter which is __u64 to shorter data type.  reiser4_statfs() sets
kstatfs->f_ffree to a large value which is close to 2^64.

> 
> I have recently run mkfs.reiser4 on /dev/hda11 with no options.
> The reiser4progs version is 0.4.12.
> 
> I made a local clone of the 2.6-test bk tree on the new reiser4
> file system and that worked OK.
> 
> I then did a "time bk -r check -acv", twice for both reiser4 and ext3.
> Here are the results for the second run for each (I neglected to
> preserve the results for the initial bk -r check -acv):
> 
> Reiser4:
> real    1m27.774s
> user    0m33.685s
> sys     0m16.059s
> 
> Ext3:
> real    2m55.179s
> user    0m32.752s
> sys     0m5.835s
> 
> Nice work.  I'll try to break Reiser4 now.
> 
> Steven
> 
> 
> 
> 

-- 
Alex.

Re: reiser4 snapshot for August 26th.

[Steven Cole]

On Thu, 2003-08-28 at 05:46, Alex Zarochentsev wrote:
[snipped]
> > [root@spc1 /]# mount -t reiser4 /dev/hda11 /share_r4
> > [root@spc1 /]# df -T
> > Filesystem    Type   1K-blocks      Used Available Use% Mounted on
> > /dev/hda1     ext3      241116     89449    139219  40% /
> > /dev/hda9     ext3    20556656  16526188   4030468  81% /home
> > none         tmpfs      126784         0    126784   0% /dev/shm
> > /dev/hda8     ext3      241116      4711    223957   3% /tmp
> > /dev/hda6     ext3     3012204   2507596    351592  88% /usr
> > /dev/hda7     ext3      489992     70721    393971  16% /var
> > df: `/share_r4': Value too large for defined data type
> 
> I can't reproduce that.  Do you see df errors each time you mount just created
> reiser4 fs?  Can you provide additional information about your system:
> distro, libc which you used?  
> 
Yes, each time that /dev/hda11 is reiser4 and mounted, I get that error.
Other fs report OK, tested were ext2, ext3, reiserfs, jfs, xfs.  Size
is about 4G.  At some point in the past, around 2.5.60, I tested the
reiser4 snapshot, and this problem did not exist.  Unfortunately, I
don't remember what the base distro was for those tests.

Distro is Red Hat Severn (the latest RH beta).
df --version reports df (coreutils) 5.0
/lib/libc.so.6 reports 2.3.2
gcc is 3.3
kernel is 2.6.0-test4 of course.
reiser4progs is 0.4.12

> My hypothesysis is that libc statfs or df itself want to convert "free inodes"
> result parameter which is __u64 to shorter data type.  reiser4_statfs() sets
> kstatfs->f_ffree to a large value which is close to 2^64.

I also tried a copy of df version 4.5.7 from a Mandrake 9.1 system, with
exactly the same results as above.

Let me know if you have further questions.

Steven

Re: reiser4 snapshot for August 26th.

[Tupshin Harper]

Alex Zarochentsev wrote:

>On Tue, Aug 26, 2003 at 01:14:46PM -0600, Steven Cole wrote:
>  
>
>>df: `/share_r4': Value too large for defined data type
>>    
>>
>
>I can't reproduce that.  Do you see df errors each time you mount just created
>reiser4 fs?  Can you provide additional information about your system:
>distro, libc which you used?  
>
>My hypothesysis is that libc statfs or df itself want to convert "free inodes"
>result parameter which is __u64 to shorter data type.  reiser4_statfs() sets
>kstatfs->f_ffree to a large value which is close to 2^64.
>  
>
This problem is 100% reproducible for me.

mkfs.reiser4
mount
df

immediately shows the problem.

Running Debian Sid, stock kernel 2.6.0-test4 + Aug 26 reiser4 snapshot, 
Athlon XP CPU, glibc-2.3.1.

-Tupshin

Re: reiser4 snapshot for August 26th.

[Vladimir Demidov]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Steven Cole wrote:

|On Tue, 2003-08-26 at 04:22, Oleg Drokin wrote:
|
|>Hello!
|>
|>   I have just released another reiser4 snapshot that I hope all 
interested
|>   parties will try. It is released against 2.6.0-test4.
|>   You can find it at http://namesys.com/snapshots/2003.08.26
|>   I include release notes below.
|>
|>Reiser4 snapshot for 2003.08.26
|>
|
|I got this error while attempting to compile with reiser4.
|Snippet from .config follows.
|
|Steven
|
|  CC      fs/reiser4/plugin/file/tail_conversion.o

befor compile "fs/reiser4/sys_reiser4.o" yacc mast be create 
"fs/reiser4/parser/parser.code.c:"
why it not created?
Is yacc installed on your computer and patched?

|
|  CC      fs/reiser4/sys_reiser4.o
|fs/reiser4/sys_reiser4.c:54:32: parser/parser.code.c: No such file or 
directory
|fs/reiser4/sys_reiser4.c: In function `sys_reiser4':
|fs/reiser4/sys_reiser4.c:75: warning: implicit declaration of function 
`reiser4_pars_init'
|fs/reiser4/sys_reiser4.c:75: warning: assignment makes pointer from 
integer without a cast
|fs/reiser4/sys_reiser4.c:80: error: dereferencing pointer to incomplete 
type
|fs/reiser4/sys_reiser4.c:82: warning: implicit declaration of function 
`yyparse'
|fs/reiser4/sys_reiser4.c:83: warning: implicit declaration of function 
`reiser4_pars_free'
|fs/reiser4/sys_reiser4.c:66: warning: unused variable `Gencode'
|fs/reiser4/sys_reiser4.c: At top level:
|fs/reiser4/parser/parser.h:333: warning: `Fistmsg' defined but not used
|fs/reiser4/parser/parser.h:342: warning: `typesOfCommand' defined but 
not used
|fs/reiser4/parser/parser.h:354: warning: `Code' defined but not used
|make[2]: *** [fs/reiser4/sys_reiser4.o] Error 1
|make[1]: *** [fs/reiser4] Error 2
|make: *** [fs] Error 2
|[steven@spc1 linux-2.6.0-test4-r4]$ grep REISER4 .config
|CONFIG_REISER4_FS=y
|CONFIG_REISER4_FS_SYSCALL=y
|CONFIG_REISER4_LARGE_KEY=y
|# CONFIG_REISER4_CHECK is not set
|CONFIG_REISER4_USE_EFLUSH=y
|# CONFIG_REISER4_BADBLOCKS is not set
|
|
|
|

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE/Tkp21LHFcKwUya8RAkPqAKCYI9+/8nAlz/4fOrcTCdz1FfKDpwCeIP3q
aOfMgqqX7Jgo1hM5kVdTcbc=
=rzM5
-----END PGP SIGNATURE-----

Re: reiser4 snapshot 20030905 [OOPS]

[Maciej Soltysiak]

Hi,

I compiled the kernel (2.6.0-test5) without key_large support
I attached a disk /dev/hda (I'm booting off /dev/hdb)

# mkfs.reiser4 /dev/hda1
Went ok

# mount -t reiser4 /dev/hda1 /1
And here's the output. It seems unsupported keys cause null pointer
dereference.

reiser4[mount(1504)]: get_ready_format40 (fs/reiser4/plugin/disk_format/disk_format40.c:229)[nikita-3228]:
WARNING: Key format mismatch. Only small keys are supported.
Unable to handle kernel NULL pointer dereference at virtual address 00000000
 printing eip:
c01d859e
*pde = 00000000
Oops: 0000 [#1]
CPU:    0
EIP:    0060:[<c01d859e>]    Tainted: P
EFLAGS: 00010246
EIP is at unhash_unformatted_node_nolock+0x1d/0x6e
eax: 00000000   ebx: c262f800   ecx: c1060018   edx: 00000000
esi: c2684000   edi: 00000000   ebp: c1060018   esp: c2685c34
ds: 007b   es: 007b   ss: 0068
Process mount (pid: 1504, threadinfo=c2684000 task=c5f36710)
Stack: c2684000 c2684000 c01d860d c262f800 c262f800 c01f8345 c262f800 c262f800
       00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
       00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Call Trace:
 [<c01d860d>] unhash_unformatted_jnode+0x1e/0x3e
 [<c01f8345>] reiser4_invalidatepage+0xe0/0x165
 [<c013c7c3>] do_invalidatepage+0x27/0x2b
 [<c013c894>] truncate_complete_page+0xcd/0xd2
 [<c013ca80>] truncate_inode_pages+0xcd/0x306
 [<c0168bf4>] wake_up_inode+0xf/0x26
 [<c016eca3>] write_inode_now+0x6a/0xa4
 [<c0168753>] generic_forget_inode+0x12e/0x141
 [<c01687e1>] iput+0x62/0x7c
 [<c01eef6c>] done_formatted_fake+0x3b/0x5b
 [<c01f6840>] reiser4_fill_super+0x343/0x606
 [<c0156154>] get_sb_bdev+0x127/0x159
 [<c016a11b>] alloc_vfsmnt+0x87/0xb6
 [<c01f6cf7>] reiser4_get_sb+0x2f/0x33
 [<c01f64fd>] reiser4_fill_super+0x0/0x606
 [<c0156386>] do_kern_mount+0x5f/0xd1
 [<c016b386>] do_add_mount+0x95/0x176
 [<c016b6b4>] do_mount+0x155/0x1a1
 [<c016b55b>] copy_mount_options+0xf4/0xf8
 [<c016baaa>] sys_mount+0xd7/0x135
 [<c0109089>] sysenter_past_esp+0x52/0x71

Code: 8b 02 85 c0 74 1c 0f b6 0d 01 06 43 c0 80 f9 02 74 04 0f 18
 <6>note: mount[1504] exited with preempt_count 2
bad: scheduling while atomic!
Call Trace:
 [<c0118d8b>] schedule+0x3ed/0x3f2
 [<c013fc5b>] unmap_page_range+0x49/0x87
 [<c013fe5c>] unmap_vmas+0x1c3/0x231
 [<c0143fa0>] exit_mmap+0x7c/0x191
 [<c011a64d>] mmput+0x67/0xb6
 [<c011e366>] do_exit+0x12e/0x3d4
 [<c010a121>] do_divide_error+0x0/0xfb
 [<c0116b62>] do_page_fault+0x14a/0x44b
 [<c013ac01>] cache_alloc_refill+0xd0/0x209
 [<c01e46fd>] atom_init+0xc9/0xd7
 [<c01e4a05>] atom_begin_andlock+0xd7/0x15e
 [<c01e5aee>] try_capture_block+0x147/0x18f
 [<c0116a18>] do_page_fault+0x0/0x44b
 [<c0109ae5>] error_code+0x2d/0x38
 [<c01d859e>] unhash_unformatted_node_nolock+0x1d/0x6e
 [<c01d860d>] unhash_unformatted_jnode+0x1e/0x3e
 [<c01f8345>] reiser4_invalidatepage+0xe0/0x165
 [<c013c7c3>] do_invalidatepage+0x27/0x2b
 [<c013c894>] truncate_complete_page+0xcd/0xd2
 [<c013ca80>] truncate_inode_pages+0xcd/0x306
 [<c0168bf4>] wake_up_inode+0xf/0x26
 [<c016eca3>] write_inode_now+0x6a/0xa4
 [<c0168753>] generic_forget_inode+0x12e/0x141
 [<c01687e1>] iput+0x62/0x7c
 [<c01eef6c>] done_formatted_fake+0x3b/0x5b
 [<c01f6840>] reiser4_fill_super+0x343/0x606
 [<c0156154>] get_sb_bdev+0x127/0x159
 [<c016a11b>] alloc_vfsmnt+0x87/0xb6
 [<c01f6cf7>] reiser4_get_sb+0x2f/0x33
 [<c01f64fd>] reiser4_fill_super+0x0/0x606
 [<c0156386>] do_kern_mount+0x5f/0xd1
 [<c016b386>] do_add_mount+0x95/0x176
 [<c016b6b4>] do_mount+0x155/0x1a1
 [<c016b55b>] copy_mount_options+0xf4/0xf8
 [<c016baaa>] sys_mount+0xd7/0x135
 [<c0109089>] sysenter_past_esp+0x52/0x71

bad: scheduling while atomic!
Call Trace:
 [<c0118d8b>] schedule+0x3ed/0x3f2
 [<c013fc5b>] unmap_page_range+0x49/0x87
 [<c013fe5c>] unmap_vmas+0x1c3/0x231
 [<c0143fa0>] exit_mmap+0x7c/0x191
 [<c011a64d>] mmput+0x67/0xb6
 [<c011e366>] do_exit+0x12e/0x3d4
 [<c010a121>] do_divide_error+0x0/0xfb
 [<c0116b62>] do_page_fault+0x14a/0x44b
 [<c013ac01>] cache_alloc_refill+0xd0/0x209
 [<c01e46fd>] atom_init+0xc9/0xd7
 [<c01e4a05>] atom_begin_andlock+0xd7/0x15e
 [<c01e5aee>] try_capture_block+0x147/0x18f
 [<c0116a18>] do_page_fault+0x0/0x44b
 [<c0109ae5>] error_code+0x2d/0x38
 [<c01d859e>] unhash_unformatted_node_nolock+0x1d/0x6e
 [<c01d860d>] unhash_unformatted_jnode+0x1e/0x3e
 [<c01f8345>] reiser4_invalidatepage+0xe0/0x165
 [<c013c7c3>] do_invalidatepage+0x27/0x2b
 [<c013c894>] truncate_complete_page+0xcd/0xd2
 [<c013ca80>] truncate_inode_pages+0xcd/0x306
 [<c0168bf4>] wake_up_inode+0xf/0x26
 [<c016eca3>] write_inode_now+0x6a/0xa4
 [<c0168753>] generic_forget_inode+0x12e/0x141
 [<c01687e1>] iput+0x62/0x7c
 [<c01eef6c>] done_formatted_fake+0x3b/0x5b
 [<c01f6840>] reiser4_fill_super+0x343/0x606
 [<c0156154>] get_sb_bdev+0x127/0x159
 [<c016a11b>] alloc_vfsmnt+0x87/0xb6
 [<c01f6cf7>] reiser4_get_sb+0x2f/0x33
 [<c01f64fd>] reiser4_fill_super+0x0/0x606
 [<c0156386>] do_kern_mount+0x5f/0xd1
 [<c016b386>] do_add_mount+0x95/0x176
 [<c016b6b4>] do_mount+0x155/0x1a1
 [<c016b55b>] copy_mount_options+0xf4/0xf8
 [<c016baaa>] sys_mount+0xd7/0x135
 [<c0109089>] sysenter_past_esp+0x52/0x71

Re: reiser4 snapshot 20030905 [OOPS]

[Nikita Danilov]

Maciej Soltysiak writes:
 > Hi,
 > 
 > I compiled the kernel (2.6.0-test5) without key_large support
 > I attached a disk /dev/hda (I'm booting off /dev/hdb)
 > 
 > # mkfs.reiser4 /dev/hda1
 > Went ok
 > 
 > # mount -t reiser4 /dev/hda1 /1
 > And here's the output. It seems unsupported keys cause null pointer
 > dereference.

This is known problem. Actually, reiser4 mount function cannot handle
errors very well at the moment.

 > 
 > reiser4[mount(1504)]: get_ready_format40 (fs/reiser4/plugin/disk_format/disk_format40.c:229)[nikita-3228]:
 > WARNING: Key format mismatch. Only small keys are supported.
 > Unable to handle kernel NULL pointer dereference at virtual address 00000000
 >  printing eip:

[...]

 >  [<c0109089>] sysenter_past_esp+0x52/0x71
 > 

Nikita.