-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
KASAN is sad about Lua #12230
Labels
Comments
rincebrain
added
Status: Triage Needed
New issue which needs to be triaged
Type: Defect
Incorrect behavior (e.g. crash, hang)
labels
Jun 12, 2021
This was referenced Jan 6, 2022
13 tasks
This issue has been automatically marked as "stale" because it has not had any activity for a while. It will be closed in 90 days if no further activity occurs. Thank you for your contributions. |
Still true, not stale.
…On Sun, Jun 12, 2022 at 5:09 AM stale[bot] ***@***.***> wrote:
This issue has been automatically marked as "stale" because it has not had
any activity for a while. It will be closed in 90 days if no further
activity occurs. Thank you for your contributions.
—
Reply to this email directly, view it on GitHub
<#12230 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABUI7PJXHFG2GYNM6UE6CTVOWSLFANCNFSM46R2HRNA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
behlendorf
added
Bot: Not Stale
Override for the stale bot
and removed
Status: Triage Needed
New issue which needs to be triaged
labels
Jun 14, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
System information
Describe the problem you're observing
As it says on the tin,
scripts/zfs-tests.sh -T functional
with KASAN. (Though not every time, of course, that would be too easy...and I don't think this is the same one I hit the last boot...)Describe how to reproduce the problem
GOTO 10 (hi @aerusso )
Include any warning/errors/backtraces from the system logs
test-runner output (I patched it to log the second-since-boot from /proc/uptime when it logs, to ensure we can match log messages to which test was responsible):
The text was updated successfully, but these errors were encountered: