linux-unionfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: "Guerard, Vincent" <VincentGuerard@eaton.com>
Cc: Amir Goldstein <amir73il@gmail.com>,
	Miklos Szeredi <miklos@szeredi.hu>,
	overlayfs <linux-unionfs@vger.kernel.org>
Subject: Re: [EXTERNAL] Re: Copy_up function fail with ubifs on upper layer
Date: Thu, 13 Dec 2018 22:25:45 +0100	[thread overview]
Message-ID: <2028730.zAhcSu7C98@blindfold> (raw)
In-Reply-To: <D10F1B1F86300941BC976D07C04B3AA0016E5EC6@LOUTCSMB11.napa.ad.etn.com>

Am Dienstag, 11. Dezember 2018, 16:32:25 CET schrieb Guerard, Vincent:
> Indeed the patch didn't solve the problem.
> 
> I trigger this every times.
> No power cuts is involved.
> 
> Every time I try to do an operation on a file that hasn't already been copied on the upper layer, it fail when overlayfs try to set xattr. 
> I tried removing the patch in ubifs which cause the fail (https://lore.kernel.org/patchwork/patch/960502/) and everything work now.
> I also just found this patch: https://lore.kernel.org/patchwork/patch/986563/ , so I guess its safe to remove it.

Good, the revert is already upstream.
So, case closed. :-)

Thanks,
//richard

      reply	other threads:[~2018-12-13 21:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <D10F1B1F86300941BC976D07C04B3AA0016E4CC7@LOUTCSMB11.napa.ad.etn.com>
     [not found] ` <CAJfpegsAxBZ0wHLMs-oBMqf8oAFaZr5f96jgYjb1TOQ_V5fcpw@mail.gmail.com>
2018-12-10 18:54   ` [EXTERNAL] Re: Copy_up function fail with ubifs on upper layer Guerard, Vincent
2018-12-10 20:37     ` Amir Goldstein
2018-12-11  9:54       ` Richard Weinberger
2018-12-11 15:32         ` Guerard, Vincent
2018-12-13 21:25           ` Richard Weinberger [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=2028730.zAhcSu7C98@blindfold \
    --to=richard@nod.at \
    --cc=VincentGuerard@eaton.com \
    --cc=amir73il@gmail.com \
    --cc=linux-unionfs@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    /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).