From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Li Nan <linan666@huaweicloud.com>
Cc: Vladislav Efanov <VEfanov@ispras.ru>,
stable@vger.kernel.org, Jan Kara <jack@suse.com>,
lvc-project@linuxtesting.org, Jan Kara <jack@suse.cz>,
yangerkun <yangerkun@huawei.com>,
linan122@huawei.com
Subject: Re: [PATCH 5.10 1/1] udf: Handle error when adding extent to a file
Date: Tue, 5 Sep 2023 08:14:42 +0100 [thread overview]
Message-ID: <2023090520-dwelled-dullness-c3c5@gregkh> (raw)
In-Reply-To: <4c28f962-0830-1138-7b91-ef6685a56afa@huaweicloud.com>
On Tue, Sep 05, 2023 at 02:57:48PM +0800, Li Nan wrote:
> Hi Greg,
>
> Our syzbot found the this issue on v5.10, could you please pick it up
> for v5.10?
What issue? Pick what up?
There's no context here :(
next prev parent reply other threads:[~2023-09-05 15:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-15 11:34 [PATCH 5.10 1/1] udf: Handle error when adding extent to a file Vladislav Efanov
2023-09-05 6:57 ` Li Nan
2023-09-05 7:14 ` Greg Kroah-Hartman [this message]
2023-09-05 7:49 ` Li Nan
2023-09-05 7:58 ` Greg Kroah-Hartman
2023-09-05 7:59 ` Greg Kroah-Hartman
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=2023090520-dwelled-dullness-c3c5@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=VEfanov@ispras.ru \
--cc=jack@suse.com \
--cc=jack@suse.cz \
--cc=linan122@huawei.com \
--cc=linan666@huaweicloud.com \
--cc=lvc-project@linuxtesting.org \
--cc=stable@vger.kernel.org \
--cc=yangerkun@huawei.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