Re: panic: ASan: Invalid access, 1-byte read at ...

On Wed, Jun 21, 2023 at 10:06:28AM -0400, Mark Johnston wrote:
> On Wed, Jun 21, 2023 at 11:53:44AM +0200, Peter Holm wrote:
> > Just got this panic:
> > 
> > 20230621 11:15:23 all (37/912): linux.sh
> > panic: ASan: Invalid access, 1-byte read at 0xfffffe020bd78e9f, RedZonePartial(2)
> > cpuid = 1
> > time = 1687338930
> > KDB: stack backtrace:
> > db_trace_self_wrapper() at db_trace_self_wrapper+0xa5/frame 0xfffffe01f16abc10
> > kdb_backtrace() at kdb_backtrace+0xc7/frame 0xfffffe01f16abd70
> > vpanic() at vpanic+0x1d7/frame 0xfffffe01f16abe30
> > panic() at panic+0xb5/frame 0xfffffe01f16abf00
> > kasan_report() at kasan_report+0xdc/frame 0xfffffe01f16abfd0
> > pfs_lookup() at pfs_lookup+0x2c2/frame 0xfffffe01f16ac0f0
> > VOP_CACHEDLOOKUP_APV() at VOP_CACHEDLOOKUP_APV+0x91/frame 0xfffffe01f16ac130
> > vfs_cache_lookup() at vfs_cache_lookup+0x1f7/frame 0xfffffe01f16ac210
> > VOP_LOOKUP_APV() at VOP_LOOKUP_APV+0x91/frame 0xfffffe01f16ac250
> > vfs_lookup() at vfs_lookup+0xa0f/frame 0xfffffe01f16ac510
> > namei() at namei+0x679/frame 0xfffffe01f16ac690
> > vn_open_cred() at vn_open_cred+0xa94/frame 0xfffffe01f16aca10
> > kern_openat() at kern_openat+0x50d/frame 0xfffffe01f16acc70
> > linux_common_open() at linux_common_open+0x141/frame 0xfffffe01f16acd30
> > amd64_syscall() amd64_syscall+0x30f/frame 0xfffffast_syscall_common() at fast_syscall_common+0xf8/frame 0xfffffe01f16acf30
> > --- syscall (2, Linux ELF64, linux_open), rip = 0x8012ef7f0, rsp = 0x7fffffffa238, rbp = 0x7fffffffa290 ---
> > KDB: enter: panic
> > [ thread pid 31838 tid 100363 ]
> > Stopped at      kdb_enter+0x34: movq    $0,0x1e3f7c1(%rip)
> > db>
> > 
> > Details @ https://people.freebsd.org/~pho/stress/log/log0450.txt
> 
> Hi Peter,
> 
> Thanks for the report.  I believe this would be fixed by
> https://reviews.freebsd.org/D40692 .

Hi Mark,

This works for me.

- Peter