Am 10/07/2018 um 05:17 schrieb waddlesplash:
On Mon, Jul 9, 2018, 10:58 PM Rene Gollent <anevilyak@xxxxxxxxx <mailto:anevilyak@xxxxxxxxx>> wrote:
> structure itself must be there. This shouldn't ever be NULL after a
> successful mount, otherwise there are deeper problems that will simply
> be hit later.
That may very well be the case; but it's also true that users might use slightly buggy filesystem drivers, and the kernel should tolerate that fault here, no?
At any rate, this seems related to the automount changes, because as I noted in my commit message deleting my mount server settings file caused it to go away (there was an NTFS partition that had wound up in there.) I can still mount the NTFS partition on its own, so if there is a problem, it doesn't seem to be with this code then...
