Vyatta configuration system (mirror of https://github.com/vyos/vyatta-cfg.git) https://git.amelek.net/vyos/vyatta-cfg.git/atom?h=current 2022-08-13T23:35:09+00:00 2022-08-13T23:35:09+00:00 RageLtMan rageltman [at] sempervictus 2022-08-13T15:34:08+00:00 urn:sha1:28cf6fee14d3bc5f6eda2099c7eb36e43297a8a8 Kernel 5.15, and probably newer, present an EXEDEV error when the vyatta-cfg code tries to boost::filesystem::copy_file on UnionFS FUSE mounts. This completely breaks operation on newer kernels, and is therefore a blocker to the rest of the project moving on to new Linux LTS versions. Boost is complex and fraught, this code behaves inconsistently in verious operating environments, and can be a nightmare to debug. Handle the concerns above using binary streaming in C++ to copy the source to the destination if an exception occurs during the existing Boost copy_file operation. Testing: Built ISO (cloud target), packer install, booted in OpenStack on KVM, booted in AWS on Xen, verified configurations are committed in both cases and that error logs are being generated to inform users about the fall-through being utilized to write-out configurations. Notes: Logging may be dropped to avoid flooding storage on often-updated systems. It is left in-place to aid developers in debugging the root concern underpinning Boot breakage (which may impact other areas of the code). 2020-05-05T02:46:34+00:00 John Estabrook jestabro@vyos.io 2020-05-05T01:46:26+00:00 urn:sha1:dadf6384029fd6748a21832e4968261d1f7c60fd In release v1.0 of unionfs-fuse, the meta directory was renamed from .unionfs to .unionfs-fuse. Consequently, the clean up of the directory following a commit vacuously succeeds, and the meta data remains. On a subsequent commit, this hidden directory will be copied into the tmp directory structure. As permissions on the whiteout files belong solely to the user, commit actions in a multiuser environment may encounter permission errors, leading to a failure in commit. Change the meta directory name here to accord with the change in unionfs-fuse, but beware that the change is reverted in release v2.0 of unionfs-fuse. 2017-11-01T13:40:31+00:00 Kim Hagen kim.sidney@gmail.com 2017-11-01T13:40:31+00:00 urn:sha1:2c751589cc234475bcb05e8e16a7e61021c8f100 2017-11-01T12:29:33+00:00 Kim Hagen kim.sidney@gmail.com 2017-11-01T12:29:33+00:00 urn:sha1:0b2db35f54fb38ac484854d22a8b2f9460c21689 2017-10-25T20:59:24+00:00 Kim kim.sidney@gmail.com 2017-10-25T20:59:24+00:00 urn:sha1:995fab7f6ba0530e05c5ea4dc4ac4aee86b3412a 2017-10-25T20:56:54+00:00 Kim kim.sidney@gmail.com 2017-10-25T20:56:54+00:00 urn:sha1:83d46a299f26f3c1f5f7c2f73d0e0b8d4d4d6475 2017-08-28T11:32:42+00:00 Kim Hagen kim.sidney@gmail.com 2017-08-28T11:32:42+00:00 urn:sha1:512e68c8161d1ccbd4ff819d9b1d622fee650215 2015-12-16T21:15:39+00:00 Thomas Jepp tom@tomjepp.co.uk 2015-12-16T21:15:39+00:00 urn:sha1:cb788b1cba70caee3b7d1a6716a4074e3acaff0e 2015-11-23T17:12:18+00:00 Thomas Jepp tom@tomjepp.co.uk 2015-11-23T17:12:18+00:00 urn:sha1:ae41f9478892be200ecc45e2d831712136aac058 2015-07-07T06:23:57+00:00 Alex Harpin development@landsofshadow.co.uk 2015-07-07T06:21:19+00:00 urn:sha1:46639708dce06b6d779651d74e87ede4679f3780 If a configuration session is exited uncleanly, either as a result of a network disconnect / timeout or other forced quit from within config mode, the unionfs mount is left in place. These remain until the system is rebooted, giving an error when unmounting the config directory. This commit checks for old configuartion directories when a user enters config mode, removing any found that are owned by that user but not part of any active configuration seesion. Bug #564 http://bugzilla.vyos.net/show_bug.cgi?id=564