Comment # 29 on bug 909912 from Thomas Blume

(In reply to Olaf Hering from comment #28)
> (In reply to Thomas Blume from comment #26)
> > https://bugzilla.redhat.com/show_bug.cgi?id=861123
> 
> His first comment clearly shows that he does not understand (or just
> ignores) the underlying design bug:
> 
> The handling of user input for the passphrase and the result of this action
> (block device appears or not) has to come before any other step. And this
> step is independend from fstab actions. The latter may get a different
> timeout per entry (like setting it to 1sec for the entries which are known
> to come from crypt).
> 
> Again: do separation of 'provide block devs' from 'use block devs for fstab'.

Actually there is a separation.
Providing block devices is done by udev when the device appears.
Udev also controls when a device will be presented to systemd by setting the
systemd and/or SYSTEMD_READY tag.
Using the block devices is done by creating mount units via
systemd-fstab-generator.
I have to submit that in this light, it is a bit misleading that
x-systemd.device-timeout is an fstab parameter.
However, apparently does what it should do.

But coming back to the initial issue, there is already an upstream commit that
address exactly this:

http://systemd-devel.freedesktop.narkive.com/89Dn3OnK/patch-cryptsetup-generator-add-jobtimeoutsec-0-for-all-known-crypt-devices

I've checked that this is included in 13.2.
However, the code for this part has changed upstream, so we might have a
regression here.
You've reported that on 13.2 the behaviour is as expected, right?