reiserfs-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Edward Shishkin <edward.shishkin@gmail.com>
To: Serkan Kaba <serkan@gentoo.org>
Cc: reiserfs-devel@vger.kernel.org,
	Christian Kujau <lists@nerdbynature.de>,
	tbzatek@redhat.com
Subject: Re: problem with GNOME 2.30
Date: Sun, 12 Sep 2010 19:53:58 +0200	[thread overview]
Message-ID: <4C8D13B6.10807@gmail.com> (raw)
In-Reply-To: <4C8D0E22.1010300@gentoo.org>

You are deadly right.

splice, pipe2, loop devices, etc users of write_begin(),
->write_end() doesn't work properly since these new
aops was introduced.

Edward.

P.S. If someone can not wait, then feel free to fix those
aops, I'll try to help..


Serkan Kaba wrote:
> On 13-04-2010 04:23, Christian Kujau wrote:
> > So, I assume that other programs (Firefox? Openoffice? vi?) can still
> > create files on this reiser4 partition. It'd be interesting how
> Gnome is
> > trying to create files. strace(1) comes to mind, I know it will be
> messy
> > to catch all the Gnome processes, but mabe you're lucky...
> With the help of upstream, my little example program and and strace I
> got some ideas on what might be the issue.
>
> Glib started to use *splice* for copying files (changelog and upstream
> says, strace output proves)
>
> I'm attaching the example program and strace outputs with glib 2.22
> and 2.24
>


      reply	other threads:[~2010-09-12 17:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-11  4:42 problem with GNOME 2.30 Serkan Kaba
2010-04-12  0:07 ` Edward Shishkin
2010-04-13  1:23 ` Christian Kujau
2010-09-12 17:30   ` Serkan Kaba
2010-09-12 17:53     ` Edward Shishkin [this message]

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=4C8D13B6.10807@gmail.com \
    --to=edward.shishkin@gmail.com \
    --cc=lists@nerdbynature.de \
    --cc=reiserfs-devel@vger.kernel.org \
    --cc=serkan@gentoo.org \
    --cc=tbzatek@redhat.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 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).