-
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
ZFS 0.6.5.3, NULL pointer dereference in dmu_objset_sync #4116
Comments
Thanks for posting it, this looks like a new issue. Are you able to consistently reproduce this by running |
Unfortunately I am not able to reproduce it by running |
@aerusso I suspect that NULL was somehow passed as the |
I have repeated the issue by constant change volsize and refreservation properties on destination node with znapzend environment:
Repeated call trace:
SysRQ list of blocked (D state) tasks output:
so I think that I have repeat scenario. |
Call trace with debug enabled:
|
Issue repeated also on released 0.6.5.4 version.
Call trace with debug enabled:
The same behavior on master SPL and ZFS source code. |
Hello,
|
@ab-oe nice analysis and fix. Your patch looks good to me could you please open a new pull request with it. An alternate approach to resolve this would be to restructure |
Make zvol update volsize operation synchronous. There is a race condition when new transaction group is added to dp->dp_dirty_datasets list by the zap_update in the zvol_update_volsize. Meanwhile, before these dirty data are synchronized, the receive process can cause that dmu_recv_end_sync is executed. Then finally dirty data are going to be synchronized but the synchronization ends with the NULL pointer dereference error.
Hello,
I am using ZFS 0.6.5.3 with kernel 3.10. The pool structure was:
Also znapzend was configured in that environment to make backup every minute to zvoldest.
When I tried to resize zvoldest using zfs set refreservation (which hanged) I got call trace with NULL pointer dereference:
Is it know issue? If you need any more information please write.
The text was updated successfully, but these errors were encountered: