Linux-bcachefs Archive mirror
 help / color / mirror / Atom feed
From: Kent Overstreet <kent.overstreet@linux.dev>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: syzkaller@googlegroups.com,
	 Thomas Bertschinger <tahbertschinger@gmail.com>,
	Ariel Miculas <ariel.miculas@gmail.com>,
	 linux-bcachefs@vger.kernel.org
Subject: Re: syzbot for bcachefs?
Date: Thu, 4 Apr 2024 19:16:14 -0400	[thread overview]
Message-ID: <aw5elbevdhwuqr7ecap6i5hepvkjbgs5xexq7nvu2yvuhh5bpb@tmyjcruysqjf> (raw)
In-Reply-To: <CACT4Y+ZEPWbJsYvWauog95yRFuzZmA=tK-uS+aDT-x=jnc3f7Q@mail.gmail.com>

On Thu, Apr 04, 2024 at 10:33:07AM +0200, Dmitry Vyukov wrote:
> On Thu, 4 Apr 2024 at 01:59, Kent Overstreet <kent.overstreet@linux.dev> wrote:
> >
> > Hi - what would it take to get syzbot going for bcachefs?
> 
> Hi Kent,
> 
> There are 2 parts:
> 
> The easy one: we need to enable it in syzbot configs. Should we
> configure it as follows?
> 
> CONFIG_BCACHEFS_FS=y
> CONFIG_BCACHEFS_QUOTA=y
> CONFIG_BCACHEFS_ERASURE_CODING=y
> CONFIG_BCACHEFS_POSIX_ACL=y
> CONFIG_BCACHEFS_DEBUG=y
> # CONFIG_BCACHEFS_TESTS is not set
> # CONFIG_BCACHEFS_LOCK_TIME_STATS is not set
> # CONFIG_BCACHEFS_NO_LATENCY_ACCT is not set
> CONFIG_BCACHEFS_SIX_OPTIMISTIC_SPIN=y
> 
> In particular, I am interested in CONFIG_BCACHEFS_DEBUG. Does it
> really add more debug checks rather than lots of console printing w/o
> checks? Some "DEBUG" kernel configs are misleading here. Checks will
> be useful on syzbot, lots of printing not so much.

CONFIG_BCACHEFS_DEBUG adds piles of assertions and no extra console
printing :)

> Second part: syzbot will need to exercise the fs in some useful way.
> Is it just a "normal" fs with files, or something special?

It's a normal - but multi device - filesystem, similar featureset to
btrfs.

> Is it mounted from an image, or an image-less fs? If it needs images,
> how can they be created?

apt install bcachefs-tools
mkfs.bcachefs <dev>
mount <dev> /mnt

...

> "find tools/testing/ Documentation/ -name "*bcachefs*"" does not give
> me anything useful.

https://bcachefs.org/ has some docs, and the tools have a man page

Anything else you'd be interested in? Thomas was interested in working
on on-disk-image error injection, is that something that would be
useful?

Ariel's also probably going to be working on adding full image creation
to mkfs, i.e. pass it a directory - is that something that would be
useful as well?

       reply	other threads:[~2024-04-04 23:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <oxdwygzxpbpwxgl5v5hzaj7er6oxt2rlmaobkov4t23xqptqrn@gxi3nlapfini>
     [not found] ` <CACT4Y+ZEPWbJsYvWauog95yRFuzZmA=tK-uS+aDT-x=jnc3f7Q@mail.gmail.com>
2024-04-04 23:16   ` Kent Overstreet [this message]
2024-04-05 16:20     ` syzbot for bcachefs? Aleksandr Nogikh
2024-04-19  8:35       ` Dmitry Vyukov
2024-04-19 17:19         ` Kent Overstreet
2024-05-02 20:28           ` Aleksandr Nogikh
2024-05-03 15:36             ` Kent Overstreet
2024-05-03 16:31               ` Aleksandr Nogikh
2024-05-03 17:18                 ` Kent Overstreet

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=aw5elbevdhwuqr7ecap6i5hepvkjbgs5xexq7nvu2yvuhh5bpb@tmyjcruysqjf \
    --to=kent.overstreet@linux.dev \
    --cc=ariel.miculas@gmail.com \
    --cc=dvyukov@google.com \
    --cc=linux-bcachefs@vger.kernel.org \
    --cc=syzkaller@googlegroups.com \
    --cc=tahbertschinger@gmail.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 read-only IMAP folder(s) and NNTP newsgroup(s).