mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Heming Zhao <heming.zhao@suse.com>
Cc: Lizhi Xu <lizhi.xu@windriver.com>,
	joseph.qi@linux.alibaba.com, jlbec@evilplan.org,
	linux-kernel@vger.kernel.org, mark@fasheh.com,
	ocfs2-devel@lists.linux.dev,
	syzbot+ab134185af9ef88dfed5@syzkaller.appspotmail.com,
	syzkaller-bugs@googlegroups.com
Subject: Re: [PATCH V4 2/2] ocfs2: Fix possible null-ptr-deref in ocfs2_set_buffer_uptodate
Date: Wed, 21 Aug 2024 14:39:11 -0700	[thread overview]
Message-ID: <20240821143911.cec82fac50c08947523da2e6@linux-foundation.org> (raw)
In-Reply-To: <25f2be6c-3e9c-4484-a44e-d26e9c4c8a74@suse.com>

OK I think I found the correct patches - v3 of [1/2] and v4 of [2/2].

For clarity can we please have a full resend of both patches?

And let's please have a [0/n] cover letter which describes the problems
which are being addressed and which also briefly describes how they
were addressed.

Also, it appears that both of these fixes should be backported into
-stable kernels.  So let's please try to identify when these bugs were
introduced and to add a suitable Fixes: to the individual changelogs.

Thanks.

  reply	other threads:[~2024-08-21 21:39 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-18 17:06 [syzbot] [ocfs2?] WARNING: bad unlock balance in ocfs2_read_blocks syzbot
2024-08-19  2:01 ` [syzbot] " syzbot
2024-08-19  2:51 ` [PATCH] ocfs2: remove unreasonable unlock Lizhi Xu
2024-08-20  4:04   ` heming.zhao
2024-08-20  5:59     ` Lizhi Xu
2024-08-20  6:55     ` [PATCH V2 1/2] " Lizhi Xu
2024-08-20  6:55       ` [PATCH V2 2/2] ocfs2: Fix uaf in ocfs2_read_blocks Lizhi Xu
2024-08-20  7:15         ` Heming Zhao
2024-08-20  7:37           ` [PATCH V3] ocfs2: Fix uaf in ocfs2_set_buffer_uptodate Lizhi Xu
2024-08-20  8:32             ` Heming Zhao
2024-08-20  9:45               ` [PATCH V3 1/2] ocfs2: remove unreasonable unlock Lizhi Xu
2024-08-20  9:45                 ` [PATCH V3 2/2] ocfs2: Fix uaf in ocfs2_set_buffer_uptodate Lizhi Xu
2024-08-20 11:32                   ` Heming Zhao
2024-08-20 13:44                     ` [PATCH] ocfs2: remove unreasonable unlock Lizhi Xu
2024-08-21  0:08                   ` [PATCH V3 2/2] ocfs2: Fix uaf in ocfs2_set_buffer_uptodate Joseph Qi
2024-08-21  2:34                     ` Joseph Qi
2024-08-21  2:39                       ` Heming Zhao
2024-08-21  5:55                         ` Lizhi Xu
2024-08-21  6:14                           ` [PATCH V4 2/2] ocfs2: Fix possible null-ptr-deref " Lizhi Xu
2024-08-21  6:23                             ` heming.zhao
2024-08-21  6:55                               ` Lizhi Xu
2024-08-21  7:37                                 ` heming.zhao
2024-08-21  7:58                                   ` Joseph Qi
2024-08-21  9:14                                     ` Lizhi Xu
2024-08-21 11:40                                       ` Heming Zhao
2024-08-21 21:39                                         ` Andrew Morton [this message]
2024-09-02  0:54                                           ` Andrew Morton
2024-09-02  1:03                                             ` Heming Zhao
2024-09-02  2:20                                               ` Joseph Qi
2024-09-02 14:23                                                 ` Lizhi Xu
2024-08-21  7:59                             ` Joseph Qi
2024-08-20 23:55                 ` [PATCH V3 1/2] ocfs2: remove unreasonable unlock Joseph Qi
2024-08-20  7:28       ` [PATCH V2 " Heming Zhao

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=20240821143911.cec82fac50c08947523da2e6@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=heming.zhao@suse.com \
    --cc=jlbec@evilplan.org \
    --cc=joseph.qi@linux.alibaba.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizhi.xu@windriver.com \
    --cc=mark@fasheh.com \
    --cc=ocfs2-devel@lists.linux.dev \
    --cc=syzbot+ab134185af9ef88dfed5@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 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®