All of lore.kernel.org
 help / color / mirror / Atom feed
From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Jens Axboe <axboe@kernel.dk>
Cc: Ming Lei <ming.lei@redhat.com>,
	linux-block@vger.kernel.org,
	syzbot <syzbot+a5d8c609c02f508672cc@syzkaller.appspotmail.com>,
	linkinjeon@kernel.org, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org, sj1557.seo@samsung.com,
	syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [exfat?] possible deadlock in fat_count_free_clusters
Date: Wed, 20 Nov 2024 00:12:19 +0900	[thread overview]
Message-ID: <87mshv8dgs.fsf@mail.parknet.co.jp> (raw)
In-Reply-To: <85d1c1bf-623e-4b93-9e60-453c0bfa7305@kernel.dk> (Jens Axboe's message of "Tue, 19 Nov 2024 07:55:50 -0700")

Jens Axboe <axboe@kernel.dk> writes:

> FWIW, your outgoing mailer is mangling patches. I fixed it up manually,
> but probably something you want to get sorted. Download the raw one from
> lore and you can see what I mean.

Looks like at Ming Lei's reply, unicode "NARROW NO-BREAK SPACE" was
included in ">>>> On Tue, Nov 12, 2024 at 12:44?AM OGAWA Hirofumi" line?
So my mailer may be encoded as utf-8, not raw.

I'll take more care next time if possible. However, this mistake (utf-8
whitespace) may hard to prevent without machinery check somehow.

Thanks.
-- 
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>

      reply	other threads:[~2024-11-19 15:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-10 23:11 [syzbot] [exfat?] possible deadlock in fat_count_free_clusters syzbot
2024-11-11 13:07 ` OGAWA Hirofumi
2024-11-19  7:27   ` [PATCH] loop: Fix ABBA locking race (Re: [syzbot] [exfat?] possible deadlock in fat_count_free_clusters) OGAWA Hirofumi
2024-11-19 12:10   ` [syzbot] [exfat?] possible deadlock in fat_count_free_clusters Ming Lei
2024-11-19 14:18     ` Jens Axboe
2024-11-19 14:46       ` OGAWA Hirofumi
2024-11-19 14:55         ` Jens Axboe
2024-11-19 15:12           ` OGAWA Hirofumi [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=87mshv8dgs.fsf@mail.parknet.co.jp \
    --to=hirofumi@mail.parknet.co.jp \
    --cc=axboe@kernel.dk \
    --cc=linkinjeon@kernel.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ming.lei@redhat.com \
    --cc=sj1557.seo@samsung.com \
    --cc=syzbot+a5d8c609c02f508672cc@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.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 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.