user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Dominique Martinet <asmadeus@codewreck.org>
To: Eric Wong <e@80x24.org>
Cc: Julien Moutinho <julm+public-inbox@sourcephile.fr>,
	meta@public-inbox.org
Subject: Re: [PATCH] nodatacow: quiet chattr errors [was: Test failures with 1.7.0]
Date: Mon, 31 Jan 2022 12:34:00 +0900	[thread overview]
Message-ID: <YfdYqLhDVQRQ9NGT@codewreck.org> (raw)
In-Reply-To: <20220131020311.M540193@dcvr>

Eric Wong wrote on Mon, Jan 31, 2022 at 02:03:11AM +0000:
> Ah, intentionally setting BTRFS_TESTDIR to something that isn't
> btrfs will break, yes.

Ok, so this is specific to the test.
Checking now nodatacow_fh skips files with non-btrfs magic, so it looks
good to me!

I've taken a look at the code now, just one more question: I don't
understand why you've made the ioctl value depend on endianness ?
get and set are respectively
_IOR('f', 1, long) and _IOW('f', 2, long)
which translate to
(2 << 30) | (8 << 16) | ('f' << 8) | 1
(1 << 30) | (8 << 16) | ('f' << 8) | 2
so should be
0x80086601
0x40086602
regardless of endianness ? as far as I understand the memory
representation might change but values themselves are handled the same,
and I don't see anything in the defines that'd swap just the R/W bits
around, but then again I don't have any big endian machine around and
never really played with one.


That aside the code looks good to me, if you do Reviewed-by tags feel
free to add mine (Dominique Martinet <asmadeus@codewreck.org>) once that
question is answered.
If you don't care, I don't care either :)


> I suppose an explicit BAIL_OUT is in order, here:

Well, tmpfs does not have attrs so lsattr fails and this triggers this
bailout (this would also "work" for nixos tests which likely don't have
lsattr available), but for example ext4 and xfs have working lsattr so
we get another failure:

=========
$ BTRFS_TESTDIR=/boot0/test strace -o /tmp/strace -f prove -bvw t/nodatacow.t 
t/nodatacow.t .. 
ok 1 - use PublicInbox::Syscall;
not ok 2 - `C' attribute set on fd with pure Perl

#   Failed test '`C' attribute set on fd with pure Perl'
#   at t/nodatacow.t line 33.
#                   '--------------e------- /boot0/test/nodatacow-80SC/pp.f
# '
#     doesn't match '(?^:C.*\/boot0\/test\/nodatacow\-80SC\/pp\.f)'
not ok 3 - `C' attribute set on dir with pure Perl
=========


But anyway, the test itself is skipped unless BTRFS_TESTDIR is set so
this isn't really a problem, I've only tried because I'm a monkey :)

Thanks again for the support, don't hesitate to ask if you need further
info or tests for the zfs problems.
-- 
Dominique

  reply	other threads:[~2022-01-31  3:34 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-08  1:07 Test failures with 1.7.0 Julien Moutinho
2021-12-08  4:08 ` Eric Wong
2021-12-08 10:56   ` Dominique Martinet
2021-12-08 18:22     ` [PATCH] nodatacow: quiet chattr errors [was: Test failures with 1.7.0] Eric Wong
2021-12-08 21:14       ` Dominique Martinet
2021-12-08 22:01         ` Dominique Martinet
2022-01-30 21:49           ` Eric Wong
2022-01-30 23:18             ` Dominique Martinet
2022-01-31  2:03               ` Eric Wong
2022-01-31  3:34                 ` Dominique Martinet [this message]
2022-02-01  1:27                   ` Eric Wong
2021-12-09  1:37     ` Test failures with 1.7.0 Julien Moutinho
2021-12-09  2:53       ` Dominique Martinet
2022-02-01  9:37         ` Eric Wong
2022-02-01 23:27       ` FD_CLOEXEC w/ nix-shell [was: Test failures with 1.7.0] Eric Wong
2022-02-02  0:23         ` Dominique Martinet
2022-02-02  2:11           ` Dominique Martinet
2022-02-01 23:34       ` [PATCH] test_lei: use consistent locale for error messages Eric Wong
2022-02-17 21:02       ` [PATCH] t/lei-sigpipe: attempt to improve diagnostics for stuck test Eric Wong
2022-02-20  1:38         ` Julien Moutinho
2022-02-22  6:44           ` Eric Wong
2022-02-27  4:15             ` Julien Moutinho
2022-02-27  6:41               ` Julien Moutinho
2022-02-27  7:23                 ` Dominique Martinet
2022-02-27  8:04                   ` Julien Moutinho
2022-02-27 11:17                     ` [PATCH] t/lei-sigpipe: ensure SIGPIPE is unblocked for this test Eric Wong
2022-03-11 10:42                       ` [PATCH] t/lei-sigpipe.t: ensure SIGPIPE is not ignored instead of not blocked Julien Moutinho
2022-03-14 22:14                         ` Eric Wong
2022-03-15  2:56                           ` Julien Moutinho
2022-03-01  2:30   ` Test failures with 1.7.0 Julien Moutinho
2022-03-01  4:05     ` Eric Wong

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

  List information: https://public-inbox.org/README

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YfdYqLhDVQRQ9NGT@codewreck.org \
    --to=asmadeus@codewreck.org \
    --cc=e@80x24.org \
    --cc=julm+public-inbox@sourcephile.fr \
    --cc=meta@public-inbox.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/public-inbox.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).