https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276770
--- Comment #2 from Qiushi <w290680...@gmail.com> --- Comment on attachment 248120 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=248120 The potential NULL dereferences The allocation functions that can return NULL pointer Potential Buggy Point Potential buggy uses (the returned pointers are not properly checked) cam_simq_alloc sys/cam/cam_xpt.c +910 devq = cam_simq_alloc(16); nvme_allocate_request_vaddr sys/dev/nvme/nvme_ctrlr_cmd.c +39 req = nvme_allocate_request_vaddr(payload, sizeof(struct nvme_controller_data), cb_fn, cb_arg); nvme_allocate_request_vaddr sys/dev/nvme/nvme_ctrlr_cmd.c +63 req = nvme_allocate_request_vaddr(payload, sizeof(struct nvme_namespace_data), cb_fn, cb_arg); nvme_allocate_request_vaddr sys/dev/nvme/nvme_ctrlr_cmd.c +262 req = nvme_allocate_request_vaddr(payload, payload_size, cb_fn, cb_arg); nvme_allocate_request_vaddr sys/dev/nvme/nvme_ctrlr.c +1256/+1259 req = nvme_allocate_request_vaddr(buf->b_data, pt->len, nvme_pt_done, pt); devfs_alloc sys/kern/kern_conf.c +1331 ndev = devfs_alloc(MAKEDEV_WAITOK); -- You are receiving this mail because: You are the assignee for the bug.
