All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jun Nie <jun.nie@linaro.org>
To: "yebin (H)" <yebin10@huawei.com>
Cc: Ye Bin <yebin@huaweicloud.com>,
	tytso@mit.edu, adilger.kernel@dilger.ca,
	linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
	jack@suse.cz,
	syzbot+4faa160fa96bfba639f8@syzkaller.appspotmail.com
Subject: Re: [PATCH v2] ext4: fix kernel BUG in 'ext4_write_inline_data_end()'
Date: Wed, 7 Dec 2022 16:11:01 +0800	[thread overview]
Message-ID: <CABymUCMC=8PwrqetiOBVK98iwKrycAf_eYZdfqVOPya6jZTPvQ@mail.gmail.com> (raw)
In-Reply-To: <63904686.3010903@huawei.com>

yebin (H) <yebin10@huawei.com> 于2022年12月7日周三 15:54写道:
>
>
>
> On 2022/12/7 14:44, Jun Nie wrote:
> > Hi Bin,
> >
> > Thanks for the patch! The bug is reproduced with this patch. I can
> > help trigger another
> > test when you have new patch.
> > https://syzkaller.appspot.com/text?tag=CrashLog&x=16760797880000
>
> The cause of this issue is different from that of the previous issue.
> I analyze that the issue
> "https://syzkaller.appspot.com/text?tag=CrashLog&x=16760797880000 "
> is caused by the concurrency of  inline data conversion and buffer
> write. To be honest, I haven't
> thought of any good solution.
>
Thanks for explanation. So the patch to fix the previous bug is still
in upstream plan, right?
> >
> > Regards,
> > Jun
> > .
>

      reply	other threads:[~2022-12-07  8:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-06 14:41 [PATCH v2] ext4: fix kernel BUG in 'ext4_write_inline_data_end()' Ye Bin
2022-12-07  6:44 ` Jun Nie
2022-12-07  7:53   ` yebin (H)
2022-12-07  8:11     ` Jun Nie [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='CABymUCMC=8PwrqetiOBVK98iwKrycAf_eYZdfqVOPya6jZTPvQ@mail.gmail.com' \
    --to=jun.nie@linaro.org \
    --cc=adilger.kernel@dilger.ca \
    --cc=jack@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzbot+4faa160fa96bfba639f8@syzkaller.appspotmail.com \
    --cc=tytso@mit.edu \
    --cc=yebin10@huawei.com \
    --cc=yebin@huaweicloud.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.