From: Masami Hiramatsu <mhiramat@kernel.org>
To: Marek Szyprowski <m.szyprowski@samsung.com>
Cc: Pawel Osciak <pawel@osciak.com>,
Kyungmin Park <kyungmin.park@samsung.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
orito.takao@socionext.com,
Fumihiro ATSUMI <atsumi@infinitegra.co.jp>
Subject: Re: [PATCH] [BUGFIX] media: vb2: Fix videobuf2 to map correct area
Date: Mon, 5 Feb 2018 22:51:05 +0900 [thread overview]
Message-ID: <20180205225105.6eb3a8e5ed93c87bf6cfd14e@kernel.org> (raw)
In-Reply-To: <2af9a288-86e8-100a-4459-bc913f3cb99d@samsung.com>
On Mon, 05 Feb 2018 09:47:46 +0100
Marek Szyprowski <m.szyprowski@samsung.com> wrote:
> Hi Masami,
>
> On 2018-02-05 03:30, Masami Hiramatsu wrote:
> > Fixes vb2_vmalloc_get_userptr() to ioremap correct area.
> > Since the current code does ioremap the page address, if the offset > 0,
> > it does not do ioremap the last page and results in kernel panic.
> >
> > This fixes to pass the page address + offset to ioremap so that ioremap
> > can map correct area. Also, this uses __pfn_to_phys() to get the physical
> > address of given PFN.
> >
> > Signed-off-by: Masami Hiramatsu <mhiramat@kernel.org>
> > Reported-by: Takao Orito <orito.takao@socionext.com>
> > ---
> > drivers/media/v4l2-core/videobuf2-vmalloc.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/media/v4l2-core/videobuf2-vmalloc.c b/drivers/media/v4l2-core/videobuf2-vmalloc.c
> > index 3a7c80cd1a17..896f2f378b40 100644
> > --- a/drivers/media/v4l2-core/videobuf2-vmalloc.c
> > +++ b/drivers/media/v4l2-core/videobuf2-vmalloc.c
> > @@ -106,7 +106,7 @@ static void *vb2_vmalloc_get_userptr(struct device *dev, unsigned long vaddr,
> > if (nums[i-1] + 1 != nums[i])
> > goto fail_map;
> > buf->vaddr = (__force void *)
> > - ioremap_nocache(nums[0] << PAGE_SHIFT, size);
> > + ioremap_nocache(__pfn_to_phys(nums[0]) + offset, size);
>
> Thanks for reporting this issue. However the above line doesn't look like
> a proper fix. Please note that at the end of that function there is already
> "buf->vaddr += offset;".
I see.
>
> IMHO the proper fix is to create a larger mapping, which would include the
> in-page start offset:
>
> ioremap_nocache(__pfn_to_phys(nums[0]), offset + size);
Yes, sorry it's my mistake. I misunderstood ioremap_nocache(addr, size) remaps
the PAGE of addr to PAGE of (addr+size). Yours is correct.
Thank you,
> BTW, thanks for updating "<< PAGE_SHIFT" to better __pfn_to_phys() macro!
>
> > } else {
> > buf->vaddr = vm_map_ram(frame_vector_pages(vec), n_pages, -1,
> > PAGE_KERNEL);
> >
> >
> >
> >
>
> Best regards
> --
> Marek Szyprowski, PhD
> Samsung R&D Institute Poland
>
--
Masami Hiramatsu <mhiramat@kernel.org>
prev parent reply other threads:[~2018-02-05 13:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20180205023108epcas5p18456b3ecc412b6709dc27fe5af14b1f6@epcas5p1.samsung.com>
2018-02-05 2:30 ` [PATCH] [BUGFIX] media: vb2: Fix videobuf2 to map correct area Masami Hiramatsu
2018-02-05 4:54 ` Masami Hiramatsu
2018-02-05 8:47 ` Marek Szyprowski
2018-02-05 13:51 ` Masami Hiramatsu [this message]
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=20180205225105.6eb3a8e5ed93c87bf6cfd14e@kernel.org \
--to=mhiramat@kernel.org \
--cc=atsumi@infinitegra.co.jp \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=mchehab@kernel.org \
--cc=orito.takao@socionext.com \
--cc=pawel@osciak.com \
/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.