From: Pete Zaitcev <zaitcev@redhat.com>
To: "Kirill A. Shutemov" <kirill@shutemov.name>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-mm@kvack.org, linux-usb@vger.kernel.org,
Pete Zaitcev <zaitcev@redhat.com>
Subject: Re: kernel BUG at ./include/linux/mm.h:LINE! (3)
Date: Wed, 3 Jan 2018 15:04:19 -0600 [thread overview]
Message-ID: <20180103150419.2fefd759@lembas.zaitcev.lan> (raw)
In-Reply-To: <20180103092604.5y4bvh3i644ts3zm@node.shutemov.name>
On Wed, 3 Jan 2018 12:26:04 +0300
"Kirill A. Shutemov" <kirill@shutemov.name> wrote:
> > > +++ b/drivers/usb/mon/mon_bin.c
> > > @@ -1228,15 +1228,24 @@ static void mon_bin_vma_close(struct vm_area_struct *vma)
> > > static int mon_bin_vma_fault(struct vm_fault *vmf)
> > > {
> > > struct mon_reader_bin *rp = vmf->vma->vm_private_data;
> > > - unsigned long offset, chunk_idx;
> > > + unsigned long offset, chunk_idx, flags;
> > > struct page *pageptr;
> > >
> > > + mutex_lock(&rp->fetch_lock);
> > > + spin_lock_irqsave(&rp->b_lock, flags);
> > > offset = vmf->pgoff << PAGE_SHIFT;
> > > - if (offset >= rp->b_size)
> > > + if (offset >= rp->b_size) {
> > > + spin_unlock_irqrestore(&rp->b_lock, flags);
> > > + mutex_unlock(&rp->fetch_lock);
> > > return VM_FAULT_SIGBUS;
> > > + }
> > > chunk_idx = offset / CHUNK_SIZE;
> > > +
> > > pageptr = rp->b_vec[chunk_idx].pg;
> > > get_page(pageptr);
> > > + spin_unlock_irqrestore(&rp->b_lock, flags);
> > > + mutex_unlock(&rp->fetch_lock);
> > > +
> > > vmf->page = pageptr;
> > > return 0;
> > > }
> >
> > I think that grabbing the spinlock is not really necessary in
> > this case. [...]
>
> Please, double check everything. I remember that the mutex wasn't enough
> to stop bug from triggering. But I didn't spend much time understanding
> the code.
I just don't understand why. The only two fields that are used
in the fault routine are rp->b_vec and rp->b_size. They are
protected by the mutex rp->fetch_lock. I don't see anything else
can spill into these fields by dirtying adjacent words in memory,
either.... except this:
case MON_IOCQ_RING_SIZE:
ret = rp->b_size;
break;
In the old days, this was safe, but who knows what CPUs do today.
It needs the same mutex taken around the read-only reference too.
How about this:
diff --git a/drivers/usb/mon/mon_bin.c b/drivers/usb/mon/mon_bin.c
index f6ae753ab99b..cb3612f28804 100644
--- a/drivers/usb/mon/mon_bin.c
+++ b/drivers/usb/mon/mon_bin.c
@@ -1004,7 +1004,9 @@ static long mon_bin_ioctl(struct file *file, unsigned int cmd, unsigned long arg
break;
case MON_IOCQ_RING_SIZE:
+ mutex_lock(&rp->fetch_lock);
ret = rp->b_size;
+ mutex_unlock(&rp->fetch_lock);
break;
case MON_IOCT_RING_SIZE:
@@ -1231,12 +1233,15 @@ static int mon_bin_vma_fault(struct vm_fault *vmf)
unsigned long offset, chunk_idx;
struct page *pageptr;
+ mutex_lock(&rp->fetch_lock);
offset = vmf->pgoff << PAGE_SHIFT;
if (offset >= rp->b_size)
+ mutex_unlock(&rp->fetch_lock);
return VM_FAULT_SIGBUS;
chunk_idx = offset / CHUNK_SIZE;
pageptr = rp->b_vec[chunk_idx].pg;
get_page(pageptr);
+ mutex_unlock(&rp->fetch_lock);
vmf->page = pageptr;
return 0;
}
-- Pete
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2018-01-03 21:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-29 0:03 Fw: " Andrew Morton
2017-12-29 13:24 ` Kirill A. Shutemov
2018-01-03 7:02 ` Pete Zaitcev
2018-01-03 9:26 ` Kirill A. Shutemov
2018-01-03 21:04 ` Pete Zaitcev [this message]
2018-01-03 21:08 ` Matthew Wilcox
2018-01-04 0:42 ` Pete Zaitcev
2018-01-08 21:25 ` Pete Zaitcev
2018-01-08 21:46 ` [PATCH] The usbmon triggers a BUG in ./include/linux/mm.h Pete Zaitcev
2018-01-09 15:03 ` Greg Kroah-Hartman
2018-01-08 5:22 ` kernel BUG at ./include/linux/mm.h:LINE! (3) Pete Zaitcev
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=20180103150419.2fefd759@lembas.zaitcev.lan \
--to=zaitcev@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=kirill@shutemov.name \
--cc=linux-mm@kvack.org \
--cc=linux-usb@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox