From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 4/4] syscalls/fanotify15: verify fid for dirent events
Date: Thu, 18 Apr 2019 21:42:47 +0200 [thread overview]
Message-ID: <20190418194247.GF8766@rei> (raw)
In-Reply-To: <CAOQ4uxhYwfE+oCHcWHCK++bqjy_gyda55Put2PD=Ui7OUua-KA@mail.gmail.com>
Hi!
> Don't know about that, but the fact is that mkfs.xfs refuses to format
> a device that has an existing filesystem on it without the -f flag.
>
> Does that ring a bell?
It does, but we clean up first 512kB of the block device prior to call
to mkfs.xfs exactly to avoid that.
> I think it may be because I upgraded xfsprogs to v4.20.
Quite likely.
> Maybe that's a mkfs.xfs bug.
Possibly.
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2019-04-18 19:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-02 10:01 [LTP] [PATCH 0/4] fanotify: FAN_REPORT_FID and Directory Modification Events Matthew Bobrowski
2019-04-02 10:01 ` [LTP] [PATCH 1/4] syscalls/fanotify01: add FAN_REPORT_FID test cases Amir Goldstein
2019-04-15 15:18 ` Cyril Hrubis
2019-04-02 10:02 ` [LTP] [PATCH 2/4] syscalls/fanotify13: new test to verify FAN_REPORT_FID functionality Matthew Bobrowski
2019-04-16 13:41 ` Cyril Hrubis
2019-04-16 14:23 ` Amir Goldstein
2019-04-19 8:37 ` Matthew Bobrowski
2019-04-19 9:07 ` Amir Goldstein
2019-04-02 10:02 ` [LTP] [PATCH 3/4] syscalls/fanotify14: new test to validate FAN_REPORT_FID interface return values Matthew Bobrowski
2019-04-16 14:04 ` Cyril Hrubis
2019-04-19 8:38 ` Matthew Bobrowski
2019-04-02 10:02 ` [LTP] [PATCH 4/4] syscalls/fanotify15: verify fid for dirent events Matthew Bobrowski
2019-04-16 14:29 ` Cyril Hrubis
2019-04-16 14:59 ` Amir Goldstein
2019-04-16 15:00 ` Cyril Hrubis
2019-04-18 18:36 ` Amir Goldstein
2019-04-18 18:58 ` Cyril Hrubis
2019-04-18 19:10 ` Amir Goldstein
2019-04-18 19:42 ` Cyril Hrubis [this message]
2019-04-19 7:18 ` Amir Goldstein
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=20190418194247.GF8766@rei \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
/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.