From: Jason Gunthorpe <jgg@nvidia.com>
To: lkp@lists.01.org
Subject: Re: d2f94f97f5 ("RDMA/ucma: Fix locking for ctx->events_reported"): -- System haltedBUG: kernel hang in boot stage
Date: Sat, 22 Aug 2020 20:09:09 -0300 [thread overview]
Message-ID: <20200822230909.GE1152540@nvidia.com> (raw)
In-Reply-To: <5f3f5a83.MjXkj0e+fMqCb8Om%lkp@intel.com>
[-- Attachment #1: Type: text/plain, Size: 3000 bytes --]
On Fri, Aug 21, 2020 at 01:24:19PM +0800, kernel test robot wrote:
> Greetings,
>
> 0day kernel testing robot got the below dmesg and the first bad commit is
>
> https://git.kernel.org/pub/scm/linux/kernel/git/leon/linux-rdma.git rdma-next
>
> commit d2f94f97f51fda759be8a562068a181f735ecd35
> Author: Jason Gunthorpe <jgg@nvidia.com>
> AuthorDate: Wed Jul 8 15:54:56 2020 -0300
> Commit: Leon Romanovsky <leonro@nvidia.com>
> CommitDate: Mon Aug 17 11:07:15 2020 +0300
>
> RDMA/ucma: Fix locking for ctx->events_reported
>
> This value is locked under the file->mut, ensure it is held whenever
> touching it.
>
> The case in ucma_migrate_id() is a race, while in ucma_free_uctx() it is
> already not possible for the write side to run, the movement is just for
> clarity.
>
> Fixes: 88314e4dda1e ("RDMA/cma: add support for rdma_migrate_id()")
> Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>
> Signed-off-by: Leon Romanovsky <leonro@mellanox.com>
>
> 097a66c338 RDMA/ucma: Fix the locking of ctx->file
> d2f94f97f5 RDMA/ucma: Fix locking for ctx->events_reported
> +---------------------------------------------+------------+------------+
> | | 097a66c338 | d2f94f97f5 |
> +---------------------------------------------+------------+------------+
> | boot_successes | 30 | 0 |
> | boot_failures | 3 | 11 |
> | BUG:kernel_NULL_pointer_dereference,address | 3 | |
> | System_halted | 0 | 11 |
> +---------------------------------------------+------------+------------+
>
> If you fix the issue, kindly add following tag
> Reported-by: kernel test robot <lkp@intel.com>
>
>
> Decompressing Linux...
>
> ZSTD-compressed data is corrupt
>
> Linux version 5.9.0-rc1-00029-gd2f94f97f51fd #2
> Command line: root=/dev/ram0 hung_task_panic=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 link=/cephfs/kbuild/run-queue/yocto-vm-yocto/i386-randconfig-a006-20200818/leon-rdma:testing:rdma-next:d2f94f97f51fda759be8a562068a181f735ecd35:bisect-System_halted/.vmlinuz-d2f94f97f51fda759be8a562068a181f735ecd35-20200821100828-1:yocto-vm-yocto-99 branch=leon-rdma/testing/rdma-next BOOT_IMAGE=/pkg/linux/i386-randconfig-a006-20200818/gcc-9/d2f94f97f51fda759be8a562068a181f735ecd35/vmlinuz-5.9.0-rc1-00029-gd2f94f97f51fd rcuperf.shutdown=0 watchdog_thresh=60
>
> Kboot worker: lkp-worker24
I think there is no possible way this patch could have caused failure
to decompress?
It is something else?
Jason
next prev parent reply other threads:[~2020-08-22 23:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-21 5:24 d2f94f97f5 ("RDMA/ucma: Fix locking for ctx->events_reported"): -- System haltedBUG: kernel hang in boot stage kernel test robot
2020-08-22 23:09 ` Jason Gunthorpe [this message]
2020-08-23 6:38 ` Leon Romanovsky
2020-08-25 5:46 ` 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=20200822230909.GE1152540@nvidia.com \
--to=jgg@nvidia.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.