From: Suraj Sonawane <surajsonawane0215@gmail.com>
To: Bart Van Assche <bvanassche@acm.org>, dgilbert@interlog.com
Cc: James.Bottomley@HansenPartnership.com,
martin.petersen@oracle.com, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org,
syzbot+7efb5850a17ba6ce098b@syzkaller.appspotmail.com
Subject: Re: [PATCH] scsi: sg: fix slab-use-after-free Read in sg_release
Date: Tue, 26 Nov 2024 10:49:03 +0530 [thread overview]
Message-ID: <fa2b0f11-d8bc-4d7c-b6dd-435eeacd6d37@gmail.com> (raw)
In-Reply-To: <dc9ee4e6-5410-4635-9970-d0b2a5d02d81@acm.org>
On 11/25/24 22:33, Bart Van Assche wrote:
> On 11/25/24 6:30 AM, Suraj Sonawane wrote:
>> Hello!
>
> Which person are you addressing with this email?
>
I apologize for not clarifying earlier—my email was intended for
everyone who might be reviewing the patch.
>> I wanted to follow up on the patch I submitted. I was wondering if you
>> had a chance to review it and if there are any comments or feedback.
>
> Sending a ping after 5 days is too quick. I think that you should wait
> at least a week before sending a ping.
>
Thank you for pointing out that sending a follow-up after five days
might be too soon. I truly appreciate your guidance on this. The reason
for my follow-up is that, as a mentee in the Linux Kernel Bug Fixing
Program, I need to include updates on my contributions in my progress
report. I’ll make sure to wait at least a week before sending any future
follow-ups.
> Bart.
>
next prev parent reply other threads:[~2024-11-26 5:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-20 12:59 [PATCH] scsi: sg: fix slab-use-after-free Read in sg_release Suraj Sonawane
2024-11-21 20:24 ` Bart Van Assche
2024-11-25 14:30 ` Suraj Sonawane
2024-11-25 17:03 ` Bart Van Assche
2024-11-26 5:19 ` Suraj Sonawane [this message]
2024-12-05 2:17 ` Martin K. Petersen
2024-12-06 6:52 ` Suraj Sonawane
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=fa2b0f11-d8bc-4d7c-b6dd-435eeacd6d37@gmail.com \
--to=surajsonawane0215@gmail.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=bvanassche@acm.org \
--cc=dgilbert@interlog.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=syzbot+7efb5850a17ba6ce098b@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox