From: "Darrick J. Wong" <djwong@kernel.org>
To: Dave Chinner <david@fromorbit.com>
Cc: Theodore Ts'o <tytso@mit.edu>, Dmitry Vyukov <dvyukov@google.com>,
Kent Overstreet <kent.overstreet@linux.dev>,
Jan Kara <jack@suse.cz>, Kun Hu <huk23@m.fudan.edu.cn>,
jlayton@redhat.com, adilger.kernel@dilger.ca, bfields@redhat.com,
viro@zeniv.linux.org.uk, christian.brauner@ubuntu.com,
hch@lst.de, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, brauner@kernel.org,
linux-bcachefs@vger.kernel.org, syzkaller@googlegroups.com
Subject: Re: Bug: INFO_ task hung in lock_two_nondirectories
Date: Tue, 14 Jan 2025 15:23:55 -0800 [thread overview]
Message-ID: <20250114232355.GB3561231@frogsfrogsfrogs> (raw)
In-Reply-To: <Z4bVQEKdj4ouAGI4@dread.disaster.area>
On Wed, Jan 15, 2025 at 08:21:04AM +1100, Dave Chinner wrote:
> On Tue, Jan 14, 2025 at 08:57:51AM -0500, Theodore Ts'o wrote:
> > P.S. If you want to push back on this nonsense, Usenix program
> > committee chairs are very much looking for open source professionals
> > to participate on the program committees for Usenix ATC (Annual
> > Technical Conference) and FAST (File System and Storage Technologies)
> > conference.
>
> The problem is that the Usenix/FAST paper committees will not reach
> out to OSS subject matter experts to review papers that they have
> been asked to review for the conference.
>
> Let me give you a recent example of a clear failure of the FAST
> paper committee w.r.t. plagarism.
>
> The core of this paper from FAST 2022:
>
> https://www.usenix.org/conference/fast22/presentation/kim-dohyun
>
> "ScaleXFS: Getting scalability of XFS back on the ring"
>
> is based on the per-CPU CIL logging work I prototyped and posted an
> RFC for early in 2021:
>
> https://lore.kernel.org/linux-xfs/20200512092811.1846252-1-david@fromorbit.com/
>
> The main core of the improvements described in the ScaleXFS paper
> are the exact per-cpu CIL algorithm in that was contained in the
> above RFC patchset.
>
> That algorithm had serious problems that meant it was unworkable in
> practice - these didn't show up until journal recovery was tested
> and it resulted in random filesystem corruptions. I didn't
> understand the root cause of the problem until months later.
>
> These problems were all based on failures to correctly order the
> per-CPU log items in the journal due to the per-CPU CIL being
> inherently racy. The algorithm I proposed 6 months later (and
> eventually got merged in July 2022) had significant changes to the
> way the per-CPU CIL ordered operations to address these problems.
>
> IOWs, object ordering on the CIL is the single most important
> critical correctness citeria for the entire journalling algorithm
> and hence a fundamental algorithmic constraint for the per-CPU CIL
> implementation.
>
> However, the ScaleXFS paper does not make any mention of this
> fundamental algorithmic constraint - I did not publish anything
> about this constraint until the November 2022 patch set....
>
> There were more clear tell-tales in the paper that indicate
> that the "research" was based on that early per-CPU CIL RFC I
> posted, but I won't go into details.
>
> I brought this to the FAST committee almost immediately after I was
> able to review the paper (a couple of days after the FAST conference
> itself). I provided them with all the links to public postings of
> the algorithm, detailed analysis of the paper and publicly posted
> code, etc. In response, they basically did nothing and brushed my
> concerns off. It would take weeks to get any response from the paper
> committee, and the overall response really felt like the Usenix
> people simply didn't care at all about what was obviously plagarised
> work.
>
> IOWs, the Usenix/FAST peer review process for OSS related papers is
> broken, and they don't seem to care when experts from the OSS
> community actually bring clear cases of academic malpractice to
> them...
Heh, I had some pretty strong suspicions of that when I saw the paper.
--D
> -Dave.
> --
> Dave Chinner
> david@fromorbit.com
>
next prev parent reply other threads:[~2025-01-14 23:23 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-12 10:00 Kun Hu
2025-01-13 10:28 ` Jan Kara
2025-01-13 20:00 ` Kent Overstreet
2025-01-14 9:07 ` Dmitry Vyukov
2025-01-14 9:20 ` Kun Hu
2025-01-14 13:57 ` Theodore Ts'o
2025-01-14 21:21 ` Dave Chinner
2025-01-14 23:23 ` Darrick J. Wong [this message]
2025-01-15 0:38 ` Kent Overstreet
2025-01-14 13:58 ` Jan Kara
2025-01-14 15:39 ` James Bottomley
[not found] ` <D067012D-7E8D-4AD9-A0CA-66B397110989@m.fudan.edu.cn>
2025-01-14 15:09 ` Kent Overstreet
2025-01-16 9:37 ` Kun Hu
2025-01-16 14:12 ` Kent Overstreet
2025-01-24 12:22 ` Kun Hu
2025-01-24 14:15 ` Kent Overstreet
2025-01-24 18:28 ` Theodore Ts'o
2025-01-24 18:39 ` Kent Overstreet
2025-01-14 9:27 ` Kun Hu
2025-01-14 2:54 ` Kun Hu
2025-01-13 14:38 ` Christian Brauner
2025-01-13 16:19 ` Matthew Wilcox
2025-01-13 18:08 ` Darrick J. Wong
2025-01-14 8:59 ` Dmitry Vyukov
2025-01-14 23:42 ` Darrick J. Wong
2025-01-14 9:15 ` Dmitry Vyukov
2025-01-14 23:43 ` Darrick J. 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250114232355.GB3561231@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=adilger.kernel@dilger.ca \
--cc=bfields@redhat.com \
--cc=brauner@kernel.org \
--cc=christian.brauner@ubuntu.com \
--cc=david@fromorbit.com \
--cc=dvyukov@google.com \
--cc=hch@lst.de \
--cc=huk23@m.fudan.edu.cn \
--cc=jack@suse.cz \
--cc=jlayton@redhat.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller@googlegroups.com \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
/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
all inboxes | Powered by JetHome®