From: Rong Chen <rong.a.chen@intel.com>
To: lkp@lists.01.org
Subject: Re: [vfs] fd0002870b: BUG:KASAN:null-ptr-deref_in_n
Date: Wed, 12 Sep 2018 08:34:52 +0800 [thread overview]
Message-ID: <0bac086d-13a5-7275-fd08-7e9bfc58f562@intel.com> (raw)
In-Reply-To: <10338.1536697773@warthog.procyon.org.uk>
[-- Attachment #1: Type: text/plain, Size: 3251 bytes --]
On 09/12/2018 04:29 AM, David Howells wrote:
> kernel test robot <rong.a.chen@intel.com> wrote:
>
>> [ 18.568403] nfs_fs_mount+0x901/0x1220
> I don't suppose you can tell me what file and line number this corresponds to?
$ faddr2line vmlinux nfs_fs_mount+0x901
nfs_fs_mount+0x901/0x1218:
nfs_parse_devname at fs/nfs/super.c:1911
(inlined by) nfs_validate_text_mount_data at fs/nfs/super.c:2187
(inlined by) nfs_fs_mount at fs/nfs/super.c:2684
>
> Also, can you tell me what the mount parameters were? I'm not sure how to
> extract them from the information provided.
qemu command (you could get from 'bin/lkp qemu -k <bzImage> job-script'):
qemu-system-x86_64 -enable-kvm -fsdev
local,id=test_dev,path=/home/nfs/.lkp//result/boot/1/vm-kbuild-1G/debian-x86_64-2018-04-03.cgz/x86_64-randconfig-r0-09070102/gcc-6/fd0002870b453c58d0d8c195954f5049bc6675fb/0,security_model=none
-device virtio-9p-pci,fsdev=test_dev,mount_tag=9p/virtfs_mount -kernel
vmlinuz-4.19.0-rc1-00104-gfd00028 -append root=/dev/ram0 user=lkp
job=/lkp/jobs/scheduled/vm-kbuild-1G-11/boot-1-debian-x86_64-2018-04-03.cgz-fd0002870b453c58d0d8c195954f5049bc6675fb-20180910-6016-1hqt4et-1.yaml
ARCH=x86_64 kconfig=x86_64-randconfig-r0-09070102
branch=linux-devel/devel-hourly-2018090623
commit=fd0002870b453c58d0d8c195954f5049bc6675fb
BOOT_IMAGE=/pkg/linux/x86_64-randconfig-r0-09070102/gcc-6/fd0002870b453c58d0d8c195954f5049bc6675fb/vmlinuz-4.19.0-rc1-00104-gfd00028
max_uptime=600
RESULT_ROOT=/result/boot/1/vm-kbuild-1G/debian-x86_64-2018-04-03.cgz/x86_64-randconfig-r0-09070102/gcc-6/fd0002870b453c58d0d8c195954f5049bc6675fb/3
LKP_LOCAL_RUN=1 debug apic=debug sysrq_always_enabled
rcupdate.rcu_cpu_stall_timeout=100 net.ifnames=0 printk.devkmsg=on
panic=-1 softlockup_panic=1 nmi_watchdog=panic oops=panic load_ramdisk=2
prompt_ramdisk=0 drbd.minor_count=8 systemd.log_level=err
ignore_loglevel console=tty0 earlyprintk=ttyS0,115200
console=ttyS0,115200 vga=normal rw ip=dhcp
result_service=9p/virtfs_mount -initrd /home/nfs/.lkp/cache/final_initrd
-smp 2 -m 1024M -no-reboot -watchdog i6300esb -rtc base=localtime
-device e1000,netdev=net0 -netdev user,id=net0 -display none -monitor
null -serial stdio -device virtio-scsi-pci,id=scsi0 -drive
file=/tmp/vdisk-nfs/disk-vm-kbuild-1G-11-0,if=none,id=hd0,media=disk,aio=native,cache=none
-device scsi-hd,bus=scsi0.0,drive=hd0,scsi-id=1,lun=0 -drive
file=/tmp/vdisk-nfs/disk-vm-kbuild-1G-11-1,if=none,id=hd1,media=disk,aio=native,cache=none
-device scsi-hd,bus=scsi0.0,drive=hd1,scsi-id=1,lun=1 -drive
file=/tmp/vdisk-nfs/disk-vm-kbuild-1G-11-2,if=none,id=hd2,media=disk,aio=native,cache=none
-device scsi-hd,bus=scsi0.0,drive=hd2,scsi-id=1,lun=2 -drive
file=/tmp/vdisk-nfs/disk-vm-kbuild-1G-11-3,if=none,id=hd3,media=disk,aio=native,cache=none
-device scsi-hd,bus=scsi0.0,drive=hd3,scsi-id=1,lun=3 -drive
file=/tmp/vdisk-nfs/disk-vm-kbuild-1G-11-4,if=none,id=hd4,media=disk,aio=native,cache=none
-device scsi-hd,bus=scsi0.0,drive=hd4,scsi-id=1,lun=4
Best Regards,
Rong Chen
>
> Thanks,
> David
> _______________________________________________
> LKP mailing list
> LKP(a)lists.01.org
> https://lists.01.org/mailman/listinfo/lkp
WARNING: multiple messages have this Message-ID (diff)
From: Rong Chen <rong.a.chen@intel.com>
To: David Howells <dhowells@redhat.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
lkp@01.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [LKP] [vfs] fd0002870b: BUG:KASAN:null-ptr-deref_in_n
Date: Wed, 12 Sep 2018 08:34:52 +0800 [thread overview]
Message-ID: <0bac086d-13a5-7275-fd08-7e9bfc58f562@intel.com> (raw)
In-Reply-To: <10338.1536697773@warthog.procyon.org.uk>
On 09/12/2018 04:29 AM, David Howells wrote:
> kernel test robot <rong.a.chen@intel.com> wrote:
>
>> [ 18.568403] nfs_fs_mount+0x901/0x1220
> I don't suppose you can tell me what file and line number this corresponds to?
$ faddr2line vmlinux nfs_fs_mount+0x901
nfs_fs_mount+0x901/0x1218:
nfs_parse_devname at fs/nfs/super.c:1911
(inlined by) nfs_validate_text_mount_data at fs/nfs/super.c:2187
(inlined by) nfs_fs_mount at fs/nfs/super.c:2684
>
> Also, can you tell me what the mount parameters were? I'm not sure how to
> extract them from the information provided.
qemu command (you could get from 'bin/lkp qemu -k <bzImage> job-script'):
qemu-system-x86_64 -enable-kvm -fsdev
local,id=test_dev,path=/home/nfs/.lkp//result/boot/1/vm-kbuild-1G/debian-x86_64-2018-04-03.cgz/x86_64-randconfig-r0-09070102/gcc-6/fd0002870b453c58d0d8c195954f5049bc6675fb/0,security_model=none
-device virtio-9p-pci,fsdev=test_dev,mount_tag=9p/virtfs_mount -kernel
vmlinuz-4.19.0-rc1-00104-gfd00028 -append root=/dev/ram0 user=lkp
job=/lkp/jobs/scheduled/vm-kbuild-1G-11/boot-1-debian-x86_64-2018-04-03.cgz-fd0002870b453c58d0d8c195954f5049bc6675fb-20180910-6016-1hqt4et-1.yaml
ARCH=x86_64 kconfig=x86_64-randconfig-r0-09070102
branch=linux-devel/devel-hourly-2018090623
commit=fd0002870b453c58d0d8c195954f5049bc6675fb
BOOT_IMAGE=/pkg/linux/x86_64-randconfig-r0-09070102/gcc-6/fd0002870b453c58d0d8c195954f5049bc6675fb/vmlinuz-4.19.0-rc1-00104-gfd00028
max_uptime=600
RESULT_ROOT=/result/boot/1/vm-kbuild-1G/debian-x86_64-2018-04-03.cgz/x86_64-randconfig-r0-09070102/gcc-6/fd0002870b453c58d0d8c195954f5049bc6675fb/3
LKP_LOCAL_RUN=1 debug apic=debug sysrq_always_enabled
rcupdate.rcu_cpu_stall_timeout=100 net.ifnames=0 printk.devkmsg=on
panic=-1 softlockup_panic=1 nmi_watchdog=panic oops=panic load_ramdisk=2
prompt_ramdisk=0 drbd.minor_count=8 systemd.log_level=err
ignore_loglevel console=tty0 earlyprintk=ttyS0,115200
console=ttyS0,115200 vga=normal rw ip=dhcp
result_service=9p/virtfs_mount -initrd /home/nfs/.lkp/cache/final_initrd
-smp 2 -m 1024M -no-reboot -watchdog i6300esb -rtc base=localtime
-device e1000,netdev=net0 -netdev user,id=net0 -display none -monitor
null -serial stdio -device virtio-scsi-pci,id=scsi0 -drive
file=/tmp/vdisk-nfs/disk-vm-kbuild-1G-11-0,if=none,id=hd0,media=disk,aio=native,cache=none
-device scsi-hd,bus=scsi0.0,drive=hd0,scsi-id=1,lun=0 -drive
file=/tmp/vdisk-nfs/disk-vm-kbuild-1G-11-1,if=none,id=hd1,media=disk,aio=native,cache=none
-device scsi-hd,bus=scsi0.0,drive=hd1,scsi-id=1,lun=1 -drive
file=/tmp/vdisk-nfs/disk-vm-kbuild-1G-11-2,if=none,id=hd2,media=disk,aio=native,cache=none
-device scsi-hd,bus=scsi0.0,drive=hd2,scsi-id=1,lun=2 -drive
file=/tmp/vdisk-nfs/disk-vm-kbuild-1G-11-3,if=none,id=hd3,media=disk,aio=native,cache=none
-device scsi-hd,bus=scsi0.0,drive=hd3,scsi-id=1,lun=3 -drive
file=/tmp/vdisk-nfs/disk-vm-kbuild-1G-11-4,if=none,id=hd4,media=disk,aio=native,cache=none
-device scsi-hd,bus=scsi0.0,drive=hd4,scsi-id=1,lun=4
Best Regards,
Rong Chen
>
> Thanks,
> David
> _______________________________________________
> LKP mailing list
> LKP@lists.01.org
> https://lists.01.org/mailman/listinfo/lkp
next prev parent reply other threads:[~2018-09-12 0:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-11 0:47 [vfs] fd0002870b: BUG:KASAN:null-ptr-deref_in_n kernel test robot
2018-09-11 0:47 ` [LKP] " kernel test robot
2018-09-11 20:29 ` David Howells
2018-09-11 20:29 ` [LKP] " David Howells
2018-09-12 0:34 ` Rong Chen [this message]
2018-09-12 0:34 ` Rong Chen
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=0bac086d-13a5-7275-fd08-7e9bfc58f562@intel.com \
--to=rong.a.chen@intel.com \
--cc=lkp@lists.01.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.