Hello! I want to report a bug, but I have not ever reported any bugs, so I've just read REPORTING-BUGS and sorry, if I'm wrong with something... If I'm wrong, tell me, please, a correct way to report this bug. 1. Getting "Oops" error on writing data to reiserfs partition with kernel 4.4.105 2. I'm getting "Oops" message on xattr_resolve_name function on any writing to reiserfs partition in kernel 4.4.105. If I'm trying to write someting to file on reiserfs partition (for example: echo TEST > /mnt/my_partition/test.txt), I'm getting "Oops" error. I've tested other file systems (ext2, ext3, jfs) and there is no such problem. I've tested it with two motherboards (ASUS P5S800-VM and Gigabyte GA-P35C-S3) with different CPU and memory - same problem. I've tested different versions of GCC (4.3.6 and 4.8.2 - build on my LFS, 4.8.5 - build on SystemRescueCD) - same problem. I've tried to run fsck, fsck with rebuild-sb, with rebuild-tree and tried to recreate fs with mkfs.reiserfs - same problem. 3. Keywords: xattr_resolve_name, reiserfs 4.1 /proc/version contens: Linux version 4.4.105 (root@sysresccd) (gcc version 4.8.5 (Gentoo 4.8.5 p1.3, pie-0.6.2) ) #5 Tue D7 4.2 Kernel config attached to this letter (.config). 5. I have not ever seen this bug on kernel 3.X (I used 3.11.7, 3.14.25, 3.14.72, 3.16.49, 3.18.45, 3.4.4) 6. My Oops message: [ 173.423067] BUG: unable to handle kernel NULL pointer dereference at (null) [ 173.423804] IP: [<c108daa9>] xattr_resolve_name+0xf/0x3f [ 173.423804] *pdpt = 0000000036049001 *pde = 0000000000000000 [ 173.423804] Oops: 0000 [#1] [ 173.423804] CPU: 0 PID: 1 Comm: bash Not tainted 4.4.105 #5 [ 173.423804] Hardware name: System manufacturer System Product Name/P5S800-VM, BIOS 1023.003 01/07 [ 173.423804] task: f6858000 ti: f685c000 task.ti: f685c000 [ 173.423804] EIP: 0060:[<c108daa9>] EFLAGS: 00010282 CPU: 0 [ 173.423804] EIP is at xattr_resolve_name+0xf/0x3f [ 173.423804] EAX: 00000000 EBX: 00000004 ECX: 00000000 EDX: f685de34 [ 173.423804] ESI: f6412980 EDI: c1258383 EBP: f685de34 ESP: f685de20 [ 173.423804] DS: 007b ES: 007b FS: 0000 GS: 0033 SS: 0068 [ 173.423804] CR0: 80050033 CR2: 00000000 CR3: 36b20780 CR4: 000006b0 [ 173.423804] Stack: [ 173.423804] c108e57a f6412980 00000000 f685de44 c108e596 c1258383 c108e57a 00000000 [ 173.423804] f6053a00 f685de54 c1124e4b 00000000 f6412980 f685ded4 c1088864 f6426700 [ 173.423804] f6412980 c10888a6 f6858000 c117ebff 00000020 00000041 00000246 f6412780 [ 173.423804] Call Trace: [ 173.423804] [<c108e57a>] ? SyS_fremovexattr+0x51/0x51 [ 173.423804] [<c108e596>] ? generic_getxattr+0x1c/0x3f [ 173.423804] [<c108e57a>] ? SyS_fremovexattr+0x51/0x51 [ 173.423804] [<c1124e4b>] ? cap_inode_need_killpriv+0x1c/0x2e [ 173.423804] [<c1088864>] ? dentry_needs_remove_privs+0x1d/0x2f [ 173.423804] [<c10888a6>] ? file_remove_privs+0x30/0x78 [ 173.423804] [<c117ebff>] ? serial8250_start_tx+0x51/0xa8 [ 173.423804] [<c1059dbf>] ? __generic_file_write_iter+0x38/0x15d [ 173.423804] [<c1059f21>] ? generic_file_write_iter+0x3d/0xbc [ 173.423804] [<c1079c0f>] ? __vfs_write+0x66/0x8f [ 173.423804] [<c1079ce3>] ? vfs_write+0x5c/0x7e [ 173.423804] [<c1079dae>] ? SyS_write+0x3e/0x6b [ 173.423804] [<c1000cb0>] ? do_fast_syscall_32+0x79/0xb2 [ 173.423804] [<c11d17c5>] ? sysenter_past_esp+0x36/0x55 [ 173.423804] Code: 85 c0 75 15 ff 01 8b 31 85 f6 7f 0d 8b 1a 85 db 75 05 46 89 31 eb ef 89 d8 5b 1 [ 173.423804] EIP: [<c108daa9>] xattr_resolve_name+0xf/0x3f SS:ESP 0068:f685de20 [ 173.423804] CR2: 0000000000000000 [ 173.424071] ---[ end trace c73002cc1e58d294 ]--- 7. I'm reproducing Oops with any write like this: mount /dev/PARTITION_WITH_REISERFS /mnt/partition echo TEST > /mnt/partition/test.txt # And now I'm getting Oops. 8. Environment 8.1 Output of ver_linux script on SystemRescueCD: If some fields are empty or look unusual you may have an old version. Compare to the current minimal requirements in Documentation/Changes. Linux sysresccd 4.4.50-std493-i586 #2 SMP Mon Feb 20 08:15:41 UTC 2017 i686 Intel(R) Celeron(R) CPU 2.80GHz GenuineIntel GNU/Linux GNU C 4.8.5 GNU Make 4.2.1 Binutils 2.26.1 Util-linux 2.28.2 Mount 2.28.2 Module-init-tools 23 E2fsprogs 1.43.3 Jfsutils 1.1.15 Reiserfsprogs 3.6.24 reiser4progs 1.1.0 Xfsprogs 4.8.0 Pcmciautils 018 PPP 2.4.7 Linux C Library 2.23 Dynamic linker (ldd) 2.23 Linux C++ Library 6.0.19 Net-tools 1.60 Kbd 2.0.3 Console-tools 2.0.3 Sh-utils 8.25 Udev 216 Wireless-tools 30 Modules Loaded 8139cp 8139too acpi_cpufreq async_memcpy async_pq async_raid6_recov async_tx async_xor ata_generic binfmt_misc cfg80211 drm drm_kms_helper e1000 fb_sys_fops fjes gameport i2c_algo_bit i2c_sis630 linear mii multipath mxm_wmi nouveau ns558 parport parport_pc parport_serial pata_acpi pata_sis ppdev raid0 raid10 raid1 raid456 rfkill sata_sis serio_raw syscopyarea sysfillrect sysimgblt tpm tpm_tis ttm video wmi 8.2 CPU info processor : 0 vendor_id : GenuineIntel cpu family : 15 model : 4 model name : Intel(R) Celeron(R) CPU 2.80GHz stepping : 9 microcode : 0x3 cpu MHz : 2799.930 cache size : 256 KB fdiv_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 5 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dm bugs : bogomips : 5572.33 clflush size : 64 cache_alignment : 128 address sizes : 36 bits physical, 48 bits virtual power management: 8.3 I'm building monolthic kernel, so there are no modules 8.4 IO ports from /proc/ioports attached to the letter (ioports.txt). Data from /proc/iomem attached to the letter (iomem.txt). 8.5 Output of lspci -vvv attached to the letter (lspci.txt). 8.6 Information from /ports/scsi/scsi attached to the letter (scsi.txt) ------ With Best Regards, Evgeniy Shtrenyov
Attachment:
.config
Description: Binary data
Attachment:
iomem.txt
Description: Binary data
Attachment:
ioports.txt
Description: Binary data
Attachment:
lspci.txt
Description: Binary data
Attachment:
scsi.txt
Description: Binary data
