From: Viacheslav Dubeyko <slava@dubeyko.com>
To: Nguyen Ngoc Thang <ngocthang2710.1999@gmail.com>
Cc: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
Yangtao Li <frank.li@vivo.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzbot+f8ce6c197125ab9d72ce@syzkaller.appspotmail.com
Subject: Re: [PATCH v4 2/2] hfsplus: validate b-tree fork extents at mount time
Date: Wed, 16 Sep 2026 10:15:11 -0700 [thread overview]
Message-ID: <2f3de27f1a824fed104918fc2756c33663ae978c.camel@dubeyko.com> (raw)
In-Reply-To: <7d1b09519cddf5124def5fdda42a5a3c8ba4ef11.camel@dubeyko.com>
On Tue, 2026-09-15 at 16:48 -0700, Viacheslav Dubeyko wrote:
> Hi Nguyen Ngoc,
>
> Please, don't move your answers from the code where I left my
> questions. I really cannot follow to your answers and the whole
> discussion is broken. I cannot follow to your answers. I am simply
> rejecting the whole email.
>
Could you please send the formal patch v5 and we can re-start the
discussion from this point? It's really hard to continue discussion if
the questions and answers have been moved from the code context. And it
really complicates the review if you mess the discussion and new code
together. Please, send new state of the code as a formal patch but not
the part of the discussion. This mixture blows my mind.
Thanks,
Slava.
prev parent reply other threads:[~2026-09-16 17:15 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-06 15:49 [PATCH] hfsplus: fix recursive tree_lock in hfsplus_file_extend() ThangNN99
2026-09-07 17:05 ` Viacheslav Dubeyko
2026-09-07 17:15 ` ThangNN99
2026-09-07 17:26 ` Viacheslav Dubeyko
2026-09-08 11:54 ` ThangNN99
2026-09-08 17:39 ` Viacheslav Dubeyko
2026-09-09 16:20 ` Nguyen Ngoc Thang
2026-09-09 18:36 ` Viacheslav Dubeyko
2026-09-10 16:01 ` Nguyen Ngoc Thang
2026-09-10 19:20 ` Viacheslav Dubeyko
2026-09-11 11:46 ` Nguyen Ngoc Thang
2026-09-11 18:26 ` Viacheslav Dubeyko
2026-09-12 13:24 ` [PATCH v4 0/2] hfsplus: fix the extents overflow file recursive tree_lock and its root cause Nguyen Ngoc Thang
2026-09-12 13:24 ` [PATCH v4 1/2] hfsplus: fix recursive tree_lock in hfsplus_file_extend() Nguyen Ngoc Thang
2026-09-14 19:26 ` Viacheslav Dubeyko
2026-09-15 14:07 ` Nguyen Ngoc Thang
2026-09-15 23:43 ` Viacheslav Dubeyko
2026-09-12 13:24 ` [PATCH v4 2/2] hfsplus: validate b-tree fork extents at mount time Nguyen Ngoc Thang
2026-09-14 20:12 ` Viacheslav Dubeyko
2026-09-15 14:15 ` Nguyen Ngoc Thang
2026-09-15 23:48 ` Viacheslav Dubeyko
2026-09-16 17:15 ` Viacheslav Dubeyko [this message]
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=2f3de27f1a824fed104918fc2756c33663ae978c.camel@dubeyko.com \
--to=slava@dubeyko.com \
--cc=frank.li@vivo.com \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ngocthang2710.1999@gmail.com \
--cc=syzbot+f8ce6c197125ab9d72ce@syzkaller.appspotmail.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
all inboxes | Powered by JetHome®