From: Eric Dumazet <eric.dumazet@gmail.com>
To: Changli Gao <xiaosuo@gmail.com>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
Matthew Wilcox <matthew@wil.cx>, Arnd Bergmann <arnd@arndb.de>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arch@vger.kernel.org
Subject: Re: [PATCH] fs: add FD_CLOFORK and O_CLOFORK
Date: Sat, 07 May 2011 08:06:34 +0200 [thread overview]
Message-ID: <1304748394.2821.654.camel@edumazet-laptop> (raw)
In-Reply-To: <1304743740-3405-1-git-send-email-xiaosuo@gmail.com>
Le samedi 07 mai 2011 à 12:49 +0800, Changli Gao a écrit :
>
> for (i = open_files; i != 0; i--) {
> struct file *f = *old_fds++;
> if (f) {
> - get_file(f);
> + if (FD_ISSET(open_files - i, new_fdt->close_on_fork)) {
> + FD_CLR(open_files - i, new_fdt->open_fds);
> + f = NULL;
> + } else {
> + get_file(f);
> + }
> } else {
> /*
You should change the main loop to
for (i = 0; i < open_files; i++) {
struct file *f = *old_fds++;
if (f && FD_ISSET(i, new_fdt->close_on_fork))
f = NULL;
if (f)
get_file(f);
else
FD_CLR(i, new_fdt->open_fds)
rcu_assign_pointer(*new_fds++, f);
}
BTW the rcu_assign_pointer() is not necessary here, since we are the
only thread populating new_fds at this point.
spin_unlock(&oldf->file_lock); and
rcu_assign_pointer(newf->fdt, new_fdt);
make sure once new_fds is visible to other threads, all our memory
writes are committed.
sparse even warns us ;)
fs/file.c:371:3: warning: incorrect type in assignment (different address spaces)
fs/file.c:371:3: expected struct file *<noident>
fs/file.c:371:3: got struct file [noderef] <asn:4>*<noident>
I'll submit a patch in a separate thread
next prev parent reply other threads:[~2011-05-07 6:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-07 4:49 [PATCH] fs: add FD_CLOFORK and O_CLOFORK Changli Gao
2011-05-07 5:25 ` Eric Dumazet
2011-05-07 5:25 ` Eric Dumazet
2011-05-07 10:09 ` Changli Gao
2011-05-07 6:06 ` Eric Dumazet [this message]
2011-05-07 6:22 ` Changli Gao
2011-05-07 6:29 ` Eric Dumazet
2011-05-07 10:10 ` Changli Gao
2011-05-07 11:41 ` Geert Uytterhoeven
2011-05-07 12:32 ` Eric Dumazet
2011-05-07 12:32 ` Eric Dumazet
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=1304748394.2821.654.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=arnd@arndb.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=viro@zeniv.linux.org.uk \
--cc=xiaosuo@gmail.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.