From: Eric Sandeen <sandeen@redhat.com>
To: lsf-pc@lists.linux-foundation.org
Cc: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: [LSF/MM ATTEND] all things local fs
Date: Mon, 12 Jan 2015 10:16:11 -0600 [thread overview]
Message-ID: <54B3F34B.2010008@redhat.com> (raw)
I'm interested in attending this year's summit. I don't have a new
broad topic that hasn't already been suggested, but as someone who has
contributed at one time or another to xfs, ext2/3/4, and btrfs, I'd
like to be present to participate in the discussions.
While not an hour-long topic, I've recently played a bit with fs fuzzing
in ways that aren't typical; fsfuzzer was originally designed to test
kernelspace, but I've found it and similar approaches useful for userspace
- it's been fruitful for finding fsck and resize bugs, for example.
Might be a decent lightning topic, just for show and tell.
Another interest is in how filesystems behave in the face of ENOSPACE
(rather than queueing) from a thinly-provisioned volume which is out of
physical space; I think we may need to strive for more consistency here,
so some cross-fs discussions might be useful.
Thanks,
-Eric
reply other threads:[~2015-01-12 16:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=54B3F34B.2010008@redhat.com \
--to=sandeen@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.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.
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.