Linux-Fsdevel Archive on lore.kernel.org
 help / color / Atom feed
From: "Enrico Weigelt, metux IT consult" <lkml@metux.net>
To: "Pali Rohár" <pali.rohar@gmail.com>,
	util-linux@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: Help with reviewing dosfstools patches
Date: Fri, 14 Jun 2019 20:45:02 +0200
Message-ID: <6f21c79d-5a80-ce3f-513c-0799145202ea@metux.net> (raw)
In-Reply-To: <9e81aa56-358a-71e1-edc1-50781062f3a4@metux.net>

On 14.06.19 17:45, Enrico Weigelt, metux IT consult wrote:
> On 14.06.19 16:20, Enrico Weigelt, metux IT consult wrote:
> 
> <snip>
> 
> Currently working through your branches. Smells like they really deserve
> a rebase and signed-off lines.

rebased/applied your patches and got test failures:

XFAIL: check-dot_entries
========================

Test check-dot_entries
First fsck run to check and fix error...
fsck.fat 4.1+git (2017-01-24)
/DIR
  "." is not first entry. Can't fix this yet.
/DIR
  ".." is not second entry. Can't fix this yet.
check-dot_entries.img: 4 files, 3/63931 clusters
*** Error was not detected by fsck.
XFAIL check-dot_entries.fsck (exit status: 100)

XFAIL: check-huge
=================

Test check-huge
First fsck run to check and fix error...
Failed to read sector 167772191.
fsck.fat 4.1+git (2017-01-24)
Second fsck run to check if error was fixed...
Failed to read sector 167772191.
fsck.fat 4.1+git (2017-01-24)
*** Error was not fixed by fsck.
XFAIL check-huge.fsck (exit status: 1)


--mtx

-- 
Enrico Weigelt, metux IT consult
Free software and Linux embedded engineering
info@metux.net -- +49-151-27565287

  reply index

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-14 10:25 Pali Rohár
2019-06-14 14:20 ` Enrico Weigelt, metux IT consult
2019-06-14 14:25   ` Pali Rohár
2019-06-14 14:30     ` Christoph Hellwig
2019-06-14 19:08       ` Pali Rohár
2019-06-14 15:45   ` Enrico Weigelt, metux IT consult
2019-06-14 18:45     ` Enrico Weigelt, metux IT consult [this message]
2019-06-14 19:10     ` Pali Rohár

Reply instructions:

You may reply publically 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=6f21c79d-5a80-ce3f-513c-0799145202ea@metux.net \
    --to=lkml@metux.net \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pali.rohar@gmail.com \
    --cc=util-linux@vger.kernel.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

Linux-Fsdevel Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-fsdevel/0 linux-fsdevel/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-fsdevel linux-fsdevel/ https://lore.kernel.org/linux-fsdevel \
		linux-fsdevel@vger.kernel.org linux-fsdevel@archiver.kernel.org
	public-inbox-index linux-fsdevel


Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-fsdevel


AGPL code for this site: git clone https://public-inbox.org/ public-inbox