[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20251028155318.2537122-1-kuniyu@google.com>
Date: Tue, 28 Oct 2025 15:51:50 +0000
From: Kuniyuki Iwashima <kuniyu@...gle.com>
To: richardcochran@...il.com
Cc: andrew+netdev@...n.ch, davem@...emloft.net, edumazet@...gle.com,
junjie.cao@...el.com, kuba@...nel.org, linux-kernel@...r.kernel.org,
netdev@...r.kernel.org, pabeni@...hat.com,
syzbot+c8c0e7ccabd456541612@...kaller.appspotmail.com,
syzkaller-bugs@...glegroups.com, kuniyu@...gle.com, thostet@...gle.com
Subject: Re: [PATCH] ptp: guard ptp_clock_gettime() if neither gettimex64 nor
From: Richard Cochran <richardcochran@...il.com>
Date: Tue, 28 Oct 2025 07:09:41 -0700
> On Tue, Oct 28, 2025 at 05:51:43PM +0800, Junjie Cao wrote:
> > Syzbot reports a NULL function pointer call on arm64 when
> > ptp_clock_gettime() falls back to ->gettime64() and the driver provides
> > neither ->gettimex64() nor ->gettime64(). This leads to a crash in the
> > posix clock gettime path.
>
> Drivers must provide a gettime method.
>
> If they do not, then that is a bug in the driver.
AFAICT, only GVE does not have gettime() and settime(), and
Tim (CCed) was preparing a fix and mostly ready to post it.
Powered by blists - more mailing lists