All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ahmet Eray Karadag <eraykrdg1@gmail.com>
To: Heming Zhao <heming.zhao@suse.com>
Cc: mark@fasheh.com, jlbec@evilplan.org, joseph.qi@linux.alibaba.com,
	ocfs2-devel@lists.linux.dev, linux-kernel@vger.kernel.org,
	david.hunter.linux@gmail.com, skhan@linuxfoundation.org,
	syzbot+55c40ae8a0e5f3659f2b@syzkaller.appspotmail.com,
	Albin Babu Varghese <albinbabuvarghese20@gmail.com>
Subject: Re: [PATCH v3] ocfs2: Invalidate inode if i_mode is zero after block read
Date: Fri, 28 Nov 2025 17:36:06 +0300	[thread overview]
Message-ID: <aSmzVvAy4lM6BsuL@eray-kasa> (raw)
In-Reply-To: <lkeaoxtkqccd3knpskbewkbn4cimlxaufix4evugcfkplk6u4b@oi36e4iu3x3r>

Hi all,

Just a kind reminder regarding this patch.

Since We are participating in the Linux Kernel Mentorship Program and have
a nearing deadline, your feedback would be incredibly helpful for us to
move forward.

Thanks,
Ahmet Eray

  reply	other threads:[~2025-11-28 14:36 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-08 12:01 [RFT PATCH] ocfs2: Invalidate inode if i_mode is zero after block read Ahmet Eray Karadag
2025-11-11  3:44 ` Heming Zhao
2025-11-17 22:35 ` [PATCH v2] " Ahmet Eray Karadag
2025-11-19 14:27   ` Heming Zhao
2025-11-19 22:17 ` [PATCH v3] " Ahmet Eray Karadag
2025-11-20  2:32   ` Heming Zhao
2025-11-28 14:36     ` Ahmet Eray Karadag [this message]
2025-12-01  2:17       ` Heming Zhao
2025-12-02  1:25     ` Joseph Qi
2025-12-02  1:51       ` Ahmet Eray Karadag
2025-12-02  0:32 ` [PATCH v4] " Ahmet Eray Karadag
2025-12-02  2:44   ` Joseph Qi
2025-12-02  2:52     ` Heming Zhao
2025-12-02  3:52 ` [PATCH v5] " Ahmet Eray Karadag
2025-12-02  6:15   ` Heming Zhao
2025-12-02  6:16     ` Joseph Qi
2025-12-02 22:45 ` [PATCH v6] " Ahmet Eray Karadag
2025-12-03  1:04   ` Joseph Qi
  -- strict thread matches above, loose matches on Subject: below --
2025-10-22 22:27 [RFC RFT PATCH] " Ahmet Eray Karadag
2025-10-25 11:13 ` [PATCH v3] " Ahmet Eray Karadag
2025-10-25 12:24   ` Joseph Qi

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=aSmzVvAy4lM6BsuL@eray-kasa \
    --to=eraykrdg1@gmail.com \
    --cc=albinbabuvarghese20@gmail.com \
    --cc=david.hunter.linux@gmail.com \
    --cc=heming.zhao@suse.com \
    --cc=jlbec@evilplan.org \
    --cc=joseph.qi@linux.alibaba.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark@fasheh.com \
    --cc=ocfs2-devel@lists.linux.dev \
    --cc=skhan@linuxfoundation.org \
    --cc=syzbot+55c40ae8a0e5f3659f2b@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 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.