From: Al Viro <viro@ZenIV.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: George Spelvin <linux@horizon.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Update of file offset on write() etc. is non-atomic with I/O
Date: Wed, 5 Mar 2014 00:04:11 +0000 [thread overview]
Message-ID: <20140305000411.GV18016@ZenIV.linux.org.uk> (raw)
In-Reply-To: <CA+55aFy2G5e0oBNWwmEiA5VS9+bB37JRNV2=X161FKEeH_odwA@mail.gmail.com>
On Tue, Mar 04, 2014 at 01:17:50PM -0800, Linus Torvalds wrote:
> On Tue, Mar 4, 2014 at 12:00 PM, Al Viro <viro@zeniv.linux.org.uk> wrote:
> >
> > OK, with the attached set (the first one is essentially unchanged from
> > your first one), it seems to work and produce better code on all targets
> > I've tried. Comments?
>
> I'm certainly ok with it. You seem to have left the fput_light()
> function around, though, despite removing fget_[raw_]light(). That
> seems a bit silly, since there is no valid use any more apart from
> net/socket.c that now doesn't balance things properly.
There's also a pile of crap around sockfd_lookup/sockfd_put, related
to that. Moreover, there's net/compat.c, which probably ought to
have the compat syscalls themselves moved to net/socket.c (under
ifdef CONFIG_COMPAT) and switched to sockfd_lookup_light().
There's l2tp_tunnel_sock_lookup(), which is simply broken - it assumes
that if tunnel->fd still resolves to a socket, that socket must
be l2tp one. Trivial to drive into BUG_ON(), in queue_work() callback,
no less... There's bluetooth, assuming that pretty much the same
(that if it got a file descriptor that resolves to a socket, it must
be a bluetooth one). BTW, I wonder what will happen if one gives
iscsi_sw_tcp_conn_bind() descriptor of a socket of sufficiently
weird sort...
Then there's staging/usbip with its sockfd_to_socket(), which is more or
less parallel to sockfd_lookup(). And open-coded analogs in nbd and
ncpfs...
> > I've also pushed those (on top of old ocfs2 fix) into vfs.git#for-linus,
> > if you prefer to read it that way. Should propagate in a few...
>
> Should I pull?
>
> I also get the feeling that the first patch should likely be marked
> for stable. Hmm?
It should; I'll mark it such when I send a pull request. I really want
to sort the situation with sockfd_lookup() and friends out, though - at
least to the point where I would understand how painful the fixes
will be.
next prev parent reply other threads:[~2014-03-05 0:04 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-03 21:03 Update of file offset on write() etc. is non-atomic with I/O George Spelvin
2014-03-03 21:26 ` Al Viro
2014-03-03 21:52 ` Linus Torvalds
2014-03-03 22:01 ` Al Viro
2014-03-03 22:17 ` Linus Torvalds
2014-03-03 23:28 ` Al Viro
2014-03-03 23:34 ` Linus Torvalds
2014-03-03 23:42 ` Al Viro
2014-03-03 23:59 ` Linus Torvalds
2014-03-04 0:23 ` Al Viro
2014-03-04 0:42 ` Linus Torvalds
2014-03-04 1:05 ` Al Viro
2014-03-04 20:00 ` Al Viro
2014-03-04 21:17 ` Linus Torvalds
2014-03-05 0:04 ` Al Viro [this message]
2014-03-10 15:55 ` Al Viro
2014-03-03 22:55 ` Linus Torvalds
2014-03-03 23:23 ` Linus Torvalds
2014-03-03 23:39 ` Al Viro
2014-03-03 23:54 ` Linus Torvalds
2014-03-03 23:54 ` Al Viro
2014-03-04 20:11 ` Cedric Blancher
2014-03-04 0:07 ` George Spelvin
2014-05-04 7:04 ` Michael Kerrisk
[not found] <a8df285f-de7f-4a3a-9a19-e0ad07ab3a5c@blur>
2014-02-20 18:15 ` Zuckerman, Boris
2014-02-20 18:29 ` Al Viro
2014-02-21 6:01 ` Michael Kerrisk (man-pages)
-- strict thread matches above, loose matches on Subject: below --
2014-02-17 15:41 Michael Kerrisk (man-pages)
2014-02-18 13:00 ` Michael Kerrisk
2014-02-20 17:14 ` Linus Torvalds
2014-03-03 17:36 ` Linus Torvalds
2014-03-03 21:45 ` Al Viro
2014-03-03 21:56 ` Linus Torvalds
2014-03-03 22:09 ` Al Viro
2014-03-03 22:20 ` Linus Torvalds
2014-03-03 22:01 ` Linus Torvalds
2014-03-03 22:10 ` Al Viro
2014-03-03 22:22 ` Linus Torvalds
2014-03-06 15:03 ` Michael Kerrisk (man-pages)
2014-03-07 3:38 ` Yongzhi Pan
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=20140305000411.GV18016@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@horizon.com \
--cc=torvalds@linux-foundation.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).