From: Andrew Morton <akpm@linux-foundation.org>
To: "Kirill A. Shutemov" <kirill@shutemov.name>
Cc: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
linux-mm@kvack.org, Jan Kara <jack@suse.cz>
Subject: Re: [PATCH 4/5] mm: extract code to fault in a page from __get_user_pages()
Date: Mon, 21 Apr 2014 18:02:27 -0700 [thread overview]
Message-ID: <20140421180227.e372200c.akpm@linux-foundation.org> (raw)
In-Reply-To: <20140422005036.GA27749@node.dhcp.inet.fi>
On Tue, 22 Apr 2014 03:50:36 +0300 "Kirill A. Shutemov" <kirill@shutemov.name> wrote:
> On Mon, Apr 21, 2014 at 04:35:22PM -0700, Andrew Morton wrote:
> > > + ret = faultin_page(tsk, vma, start, &foll_flags,
> > > + nonblocking);
> > > + switch (ret) {
> > > + case 0:
> > > + break;
> > > + case -EFAULT:
> > > + case -ENOMEM:
> > > + case -EHWPOISON:
> > > + return i ? i : ret;
> > > + case -EBUSY:
> > > return i;
> > > + case -ENOENT:
> > > + goto next_page;
> > > + default:
> > > + BUILD_BUG();
> >
> > hm, why the BUILD_BUG?
>
> To be sure that we can catch and handle any value faultin_page() can
> return.
Well sure, but to do that we use BUG().
BUILD_BUG() will fail to build and that of course is what happened.
> Could you show resulting faultin_page() from you tree? Or I can just
> rebase it on top of your tree once it will be published if you wish.
It looked like this:
ret = faultin_page(tsk, vma, start, &foll_flags,
nonblocking);
switch (ret) {
case 0:
break;
case -EFAULT:
case -ENOMEM:
case -EHWPOISON:
return i ? i : ret;
case -EBUSY:
return i;
case -ENOENT:
goto next_page;
default:
BUILD_BUG();
}
is that what you tested?
I suspect what happened is that your gcc worked out that faultin_page()
cannot return anything other than one of those six values and so the
compiler elided the BUILD_BUG() code. But my gcc-4.4.4 isn't that smart.
For example this:
--- a/fs/open.c~a
+++ a/fs/open.c
@@ -1101,3 +1101,9 @@ int nonseekable_open(struct inode *inode
}
EXPORT_SYMBOL(nonseekable_open);
+
+void foo(void)
+{
+ if (0)
+ BUILD_BUG();
+}
compiles OK with gcc-4.4.4.
No matter, let's just leave it as a BUG().
--
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:[~2014-04-22 1:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-03 14:35 [PATCH 0/5] get_user_pages() cleanup Kirill A. Shutemov
2014-04-03 14:35 ` [PATCH 1/5] mm: move get_user_pages()-related code to separate file Kirill A. Shutemov
2014-04-03 14:35 ` [PATCH 2/5] mm: extract in_gate_area() case from __get_user_pages() Kirill A. Shutemov
2014-04-03 14:35 ` [PATCH 3/5] mm: cleanup follow_page_mask() Kirill A. Shutemov
2014-04-03 14:35 ` [PATCH 4/5] mm: extract code to fault in a page from __get_user_pages() Kirill A. Shutemov
2014-04-21 23:35 ` Andrew Morton
[not found] ` <20140422005036.GA27749@node.dhcp.inet.fi>
2014-04-22 1:02 ` Andrew Morton [this message]
[not found] ` <20140422012022.GA28319@node.dhcp.inet.fi>
2014-04-22 1:26 ` Andrew Morton
2014-04-03 14:35 ` [PATCH 5/5] mm: cleanup __get_user_pages() Kirill A. Shutemov
2014-04-18 22:22 ` [PATCH 0/5] get_user_pages() cleanup Andrew Morton
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=20140421180227.e372200c.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=jack@suse.cz \
--cc=kirill.shutemov@linux.intel.com \
--cc=kirill@shutemov.name \
--cc=linux-mm@kvack.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;
as well as URLs for NNTP newsgroup(s).