From: Matthew Wilcox <willy@infradead.org>
To: Amir Goldstein <amir73il@gmail.com>
Cc: "Darrick J. Wong" <djwong@kernel.org>,
lsf-pc@lists.linux-foundation.org, linux-fsdevel@vger.kernel.org,
xfs <linux-xfs@vger.kernel.org>,
linux-ext4 <linux-ext4@vger.kernel.org>,
linux-btrfs <linux-btrfs@vger.kernel.org>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
linux-mm@kvack.org
Subject: Re: [Lsf-pc] [LSF TOPIC] online repair of filesystems: what next?
Date: Wed, 19 Apr 2023 04:34:21 +0100 [thread overview]
Message-ID: <ZD9hPSzEign05MTZ@casper.infradead.org> (raw)
In-Reply-To: <CAOQ4uxgUOuR80jsAE2DkZhMPVNT_WwnsSX8-GSkZO4=k3VbCsw@mail.gmail.com>
On Tue, Apr 18, 2023 at 10:46:32AM +0300, Amir Goldstein wrote:
> On Tue, Apr 18, 2023 at 7:46 AM Darrick J. Wong <djwong@kernel.org> wrote:
> > TBH, most of my fs complaints these days are managerial problems (Are we
> > spending too much time on LTS? How on earth do we prioritize projects
> > with all these drive by bots?? Why can't we support large engineering
> > efforts better???) than technical.
>
> I penciled one session for "FS stable backporting (and other LTS woes)".
> I made it a cross FS/IO session so we can have this session in the big room
> and you are welcome to pull this discussion to any direction you want.
Would this make sense to include the MM folks as well? Certainly MM
has made the same choice as XFS ("No automatic backports, we will cc:
stable on patches that make sense").
next parent reply other threads:[~2023-04-19 3:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Y/5ovz6HI2Z47jbk@magnolia>
[not found] ` <CAOQ4uxj6mNbGQBSpg-KpSiDa2UugBFXki4HhM4DPvXeAQMnRWg@mail.gmail.com>
[not found] ` <20230418044641.GD360881@frogsfrogsfrogs>
[not found] ` <CAOQ4uxgUOuR80jsAE2DkZhMPVNT_WwnsSX8-GSkZO4=k3VbCsw@mail.gmail.com>
2023-04-19 3:34 ` Matthew Wilcox [this message]
2023-04-19 4:02 ` 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=ZD9hPSzEign05MTZ@casper.infradead.org \
--to=willy@infradead.org \
--cc=amir73il@gmail.com \
--cc=djwong@kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-xfs@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=martin.petersen@oracle.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