From: Pete Zaitcev <zaitcev@redhat.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: "Kirill A. Shutemov" <kirill@shutemov.name>,
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 18:42:13 -0600 [thread overview]
Message-ID: <20180103184213.711b6704@lembas.zaitcev.lan> (raw)
In-Reply-To: <20180103210812.GC3228@bombadil.infradead.org>
On Wed, 3 Jan 2018 13:08:12 -0800
Matthew Wilcox <willy@infradead.org> wrote:
> > + 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;
>
> missing braces ... maybe you'd rather a 'goto sigbus' approach?
Thanks. What a way to return to kernel programming for me. I'm going
to test it anyway, already started to unpacking a PC, but yeah...
-- 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-04 0:42 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
2018-01-03 21:08 ` Matthew Wilcox
2018-01-04 0:42 ` Pete Zaitcev [this message]
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=20180103184213.711b6704@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 \
--cc=willy@infradead.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