** Changed in: linux (Ubuntu Disco)
Status: Confirmed => Fix Released
** Changed in: linux (Ubuntu Cosmic)
Status: Confirmed => Won't Fix
** Changed in: linux (Ubuntu Bionic)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of
** Also affects: linux (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Cosmic)
Status: New => Confirmed
** Changed in: linux (Ubuntu Disco)
Status: New =>
Hi, have some news in this one. I've emailed Microsoft CIFS maintainers, they
recommended the following patch as a potential fix:
b98749cac4a6 ("CIFS: keep FileInfo handle live during oplock break").
There's a PPA with a kernel built including this patch, for those
interested in testing:
** Tags added: sts
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1795659
Title:
kernel panic using CIFS share smb2_push_mandatory_locks
Status in linux package in Ubuntu:
Confirmed
Thanks for reporting that Stefan! There's a Debian bug report (although the
kernel
version is different, seems the same issue):
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830771 .
Also, recently I had a report of this issue happening in Azure instance,
kernel version 4.15.0-1041-azure.
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I'm unable to fully test the upstream bugs as I can't install linux-
headers-4.19.0-041900rc6-generic due to libssl1.1 not being available
for 4.15. System does boot without the generic package on the new
version though.
While i'm looking at upgrading the boxes to 18.04 from the 16.04
install,
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19
8 matches
Mail list logo