We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi,
I am using exfat. But I have gotten a lot of panic errors. The panic stack is as below:
exfat_lookup&&lookup_real&__lookup_hash&walk_component&path_lookupat&filename_lookup&vfs_path_lookup&sdcardfs_lookup&lookup_real&__lookup_hash&walk_component&link_path_walk&path_lookupat&filename_lookup&user_path_at_empt
I locate the panic. It happens in the line CHECK_ERR(d_unhashed(alias)); in the following function.
CHECK_ERR(d_unhashed(alias));
#if LINUX_VERSION_CODE >= KERNEL_VERSION(3,7,00) static struct dentry *exfat_lookup(struct inode *dir, struct dentry *dentry, unsigned int flags) #else static struct dentry *exfat_lookup(struct inode *dir, struct dentry *dentry, struct nameidata *nd) #endif { ... CHECK_ERR(d_unhashed(alias)); ... }
Is it known? Do you have any solution to this issue?
Thank you.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hi,
I am using exfat. But I have gotten a lot of panic errors. The panic stack is as below:
exfat_lookup&&lookup_real&__lookup_hash&walk_component&path_lookupat&filename_lookup&vfs_path_lookup&sdcardfs_lookup&lookup_real&__lookup_hash&walk_component&link_path_walk&path_lookupat&filename_lookup&user_path_at_empt
I locate the panic. It happens in the line
CHECK_ERR(d_unhashed(alias));
in the following function.Is it known? Do you have any solution to this issue?
Thank you.
The text was updated successfully, but these errors were encountered: