On Mon, Jan 23, 2023 at 01:51:20PM +0100, Hans de Goede wrote: > If set_fmt() fails make queue_setup() actually return the error instead of > returning 0. > > This fixes the following oops on set_fmt() failures: > > [ 1060.378662] ------------[ cut here ]------------ > [ 1060.378805] WARNING: CPU: 0 PID: 2080 at drivers/media/common/videobuf2/videobuf2-core.c:840 vb2_core_reqbufs+0x3f7/0x430 [videobuf2_common] > ... > [ 1060.381414] RIP: 0010:vb2_core_reqbufs+0x3f7/0x430 [videobuf2_common] > ... > [ 1060.382066] vb2_ioctl_reqbufs+0x9d/0xe0 [videobuf2_v4l2] > [ 1060.382181] __video_do_ioctl+0x18e/0x3c0 [videodev] Should we rather keep this at the beginning of the series? Just for the logical split of fixes go first. Yes, I know that it doesn't make much sense for the staging drivers, but still grouping might help. Reviewed-by: Andy Shevchenko <andy@xxxxxxxxxx> > Signed-off-by: Hans de Goede <hdegoede@xxxxxxxxxx> > --- > drivers/staging/media/atomisp/pci/atomisp_fops.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/drivers/staging/media/atomisp/pci/atomisp_fops.c b/drivers/staging/media/atomisp/pci/atomisp_fops.c > index 4643bb0db995..682239ea042f 100644 > --- a/drivers/staging/media/atomisp/pci/atomisp_fops.c > +++ b/drivers/staging/media/atomisp/pci/atomisp_fops.c > @@ -80,7 +80,7 @@ static int atomisp_queue_setup(struct vb2_queue *vq, > > out: > mutex_unlock(&pipe->asd->isp->mutex); > - return 0; > + return ret; > } > > static int atomisp_buf_init(struct vb2_buffer *vb) > -- > 2.39.0 > -- With Best Regards, Andy Shevchenko
