From: Linus Torvalds <torvalds@linux-foundation.org>
To: Mike Waychison <mikew@google.com>
Cc: Oren Laadan <orenl@cs.columbia.edu>,
jeremy@goop.org, arnd@arndb.de, linux-api@vger.kernel.org,
containers@lists.linux-foundation.org,
linux-kernel@vger.kernel.org,
Dave Hansen <dave@linux.vnet.ibm.com>,
linux-mm@kvack.org, Alexander Viro <viro@zeniv.linux.org.uk>,
"H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>
Subject: Re: [RFC v11][PATCH 03/13] General infrastructure for checkpoint restart
Date: Tue, 16 Dec 2008 11:28:39 -0800 (PST) [thread overview]
Message-ID: <alpine.LFD.2.00.0812161116380.14014@localhost.localdomain> (raw)
In-Reply-To: <4947FBC8.2000601@google.com>
On Tue, 16 Dec 2008, Mike Waychison wrote:
>
> set_fs(fs) here
Btw, this all is an excellent example of why people should try to aim for
small functions and use lots of them.
It's often _way_ more readable to do
static inline int __some_fn(...)
{
.. do the real work here ..
}
int some_fn(...)
{
int retval;
prepare();
retval = __some_fn(..)
finish();
return retval;
}
where "prepare/finish" can be about locking, or set_fs(), or allocation
and de-allocation of temporary buffers, or any number of things like that.
With set_fs() in particular, the wrapper function also tends to be the
perfect place to change a regular (kernel) pointer into a user pointer.
IOW, it's the place to make sparse happy, where you can do things like
uptr = (__force void __user *)ptr;
and comment on the fact that the forced user pointer cast is valid only
because of the set_fs().
Because it looks like the code isn't sparse-clean.
Btw, I also think that code like this is bogus:
nwrite = file->f_op->write(file, addr, nleft, &file->f_pos);
because you're not supposed to pass in the raw file->f_pos to that
function. It's fundamentally thread-unsafe. I realize that maybe you don't
care, but the thing is, you're supposed to do
loff_t pos = file->pos;
..
nwrite = file->f_op->write(file, addr, nleft, &pos);
..
file->f_pos = pos;
and in fact preferably use "file_pos_read()" and "file_pos_write()" (but
we've never exposed them outside of fs/read_write.c, so I guess we should
do that).
And yes, I realize that some code does take the address of f_pos directly
(splice, nfsctl, others), and I realize that it works, but it's still bad
form. Please don't add more of them.
Linus
--
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:[~2008-12-16 19:27 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-05 17:31 [RFC v11][PATCH 00/13] Kernel based checkpoint/restart Oren Laadan
2008-12-05 17:31 ` [RFC v11][PATCH 01/13] Create syscalls: sys_checkpoint, sys_restart Oren Laadan
2008-12-05 17:31 ` [RFC v11][PATCH 02/13] Checkpoint/restart: initial documentation Oren Laadan
2008-12-05 17:31 ` [RFC v11][PATCH 03/13] General infrastructure for checkpoint restart Oren Laadan
2008-12-06 7:26 ` Joe Perches
2008-12-16 19:04 ` Mike Waychison
2008-12-16 19:28 ` Linus Torvalds [this message]
2008-12-16 21:54 ` Mike Waychison
2008-12-16 22:14 ` Dave Hansen
2008-12-16 22:43 ` Mike Waychison
2008-12-17 0:13 ` Dave Hansen
2008-12-16 23:42 ` Oren Laadan
2008-12-17 0:42 ` Mike Waychison
2008-12-17 2:08 ` Oren Laadan
2008-12-05 17:31 ` [RFC v11][PATCH 04/13] x86 support for checkpoint/restart Oren Laadan
2008-12-17 2:19 ` Mike Waychison
2008-12-17 15:23 ` Oren Laadan
2008-12-05 17:31 ` [RFC v11][PATCH 05/13] Dump memory address space Oren Laadan
2008-12-18 2:26 ` Mike Waychison
2008-12-18 11:10 ` Oren Laadan
2008-12-18 15:05 ` Dave Hansen
2008-12-18 15:54 ` Dave Hansen
2008-12-18 20:00 ` Oren Laadan
2008-12-18 18:15 ` Mike Waychison
2008-12-18 18:21 ` Dave Hansen
2008-12-18 20:11 ` Oren Laadan
2008-12-05 17:31 ` [RFC v11][PATCH 06/13] Restore " Oren Laadan
2008-12-05 17:31 ` [RFC v11][PATCH 07/13] Infrastructure for shared objects Oren Laadan
2008-12-05 17:31 ` [RFC v11][PATCH 08/13] Dump open file descriptors Oren Laadan
2008-12-05 17:31 ` [RFC v11][PATCH 09/13] Restore open file descriprtors Oren Laadan
2008-12-05 17:31 ` [RFC v11][PATCH 10/13] External checkpoint of a task other than ourself Oren Laadan
2008-12-05 17:31 ` [RFC v11][PATCH 11/13] Track in-kernel when we expect checkpoint/restart to work Oren Laadan
2008-12-05 17:31 ` [RFC v11][PATCH 12/13] Checkpoint multiple processes Oren Laadan
2008-12-05 17:31 ` [RFC v11][PATCH 13/13] Restart " Oren Laadan
2008-12-06 0:19 ` [RFC v11][PATCH 00/13] Kernel based checkpoint/restart Serge E. Hallyn
2008-12-09 19:42 ` Serge E. Hallyn
2008-12-16 18:43 ` Dave Hansen
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=alpine.LFD.2.00.0812161116380.14014@localhost.localdomain \
--to=torvalds@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=containers@lists.linux-foundation.org \
--cc=dave@linux.vnet.ibm.com \
--cc=hpa@zytor.com \
--cc=jeremy@goop.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mikew@google.com \
--cc=mingo@elte.hu \
--cc=orenl@cs.columbia.edu \
--cc=tglx@linutronix.de \
--cc=viro@zeniv.linux.org.uk \
/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