From: Richard Cochran <richardcochran@gmail.com>
To: Edward Adam Davis <eadavis@qq.com>
Cc: davem@davemloft.net, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, reibax@gmail.com,
syzbot+df3f3ef31f60781fa911@syzkaller.appspotmail.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [PATCH net-next V2] ptp: fix corrupted list in ptp_open
Date: Wed, 1 Nov 2023 17:12:53 -0700 [thread overview]
Message-ID: <ZULphe-5N0M5x_Kk@hoboy.vegasvil.org> (raw)
In-Reply-To: <tencent_24C96E7894D0EBA2EDD2CFB87BB66EC02D0A@qq.com>
On Tue, Oct 31, 2023 at 05:07:08AM +0800, Edward Adam Davis wrote:
> There is no lock protection when writing ptp->tsevqs in ptp_open(),
> ptp_release(), which can cause data corruption,
Really? How?
> use mutex lock to avoid this
> issue.
>
> Moreover, ptp_release() should not be used to release the queue in ptp_read(),
> and it should be deleted together.
>
> Reported-and-tested-by: syzbot+df3f3ef31f60781fa911@syzkaller.appspotmail.com
> Fixes: 8f5de6fb2453 ("ptp: support multiple timestamp event readers")
> Signed-off-by: Edward Adam Davis <eadavis@qq.com>
> ---
> drivers/ptp/ptp_chardev.c | 11 +++++++++--
> drivers/ptp/ptp_clock.c | 3 +++
> drivers/ptp/ptp_private.h | 1 +
> 3 files changed, 13 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/ptp/ptp_chardev.c b/drivers/ptp/ptp_chardev.c
> index 282cd7d24077..e31551d2697d 100644
> --- a/drivers/ptp/ptp_chardev.c
> +++ b/drivers/ptp/ptp_chardev.c
> @@ -109,6 +109,9 @@ int ptp_open(struct posix_clock_context *pccontext, fmode_t fmode)
> struct timestamp_event_queue *queue;
> char debugfsname[32];
>
> + if (mutex_lock_interruptible(&ptp->tsevq_mux))
> + return -ERESTARTSYS;
> +
This mutex is not needed.
Please don't ignore review comments.
Thanks,
Richard
next prev parent reply other threads:[~2023-11-02 0:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tencent_61372097D036524ACC74E176DF66043C2309@qq.com>
[not found] ` <tencent_D71CEB16EC1ECD0879366E9C2E216FBC950A@qq.com>
2023-10-29 19:49 ` [PATCH-net-next] " Richard Cochran
2023-10-29 19:57 ` Richard Cochran
[not found] ` <tencent_24C96E7894D0EBA2EDD2CFB87BB66EC02D0A@qq.com>
2023-10-31 9:28 ` [PATCH net-next V2] " Martin Habets
2023-11-02 0:12 ` Richard Cochran [this message]
[not found] ` <tencent_ACEACCAC786A6F282DF16DCC95C8E852ED0A@qq.com>
2023-11-03 23:15 ` Richard Cochran
[not found] <tencent_2C67C6D2537B236F497823BCC457976F9705@qq.com>
2023-11-02 0:18 ` Richard Cochran
2023-11-02 18:16 ` Jeremy Cline
2023-11-04 2:13 ` Richard Cochran
2023-11-04 2:15 ` Richard Cochran
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=ZULphe-5N0M5x_Kk@hoboy.vegasvil.org \
--to=richardcochran@gmail.com \
--cc=davem@davemloft.net \
--cc=eadavis@qq.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=reibax@gmail.com \
--cc=syzbot+df3f3ef31f60781fa911@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®