{"push_id":734660095,"size":60,"distinct_size":1,"ref":"refs/heads/tuxonice-4.0","head":"ef18ec5fffb7161623673ab6f944d5cf2f049282","before":"4ea7ec998d91b1169dee27e86e1a9ea5e72a01c6","commits":[{"sha":"bb9fcac1598aeecc9079c467850b01e1c2515124","author":{"email":"8a741aa8cbd77ebc4a56ddb528ce9fd15d42f034@xmission.com","name":"Eric W. Biederman"},"message":"fs: Add helper functions for permanently empty directories.\n\ncommit fbabfd0f4ee2e8847bf56edf481249ad1bb8c44d upstream.\n\nTo ensure it is safe to mount proc and sysfs I need to check if\nfilesystems that are mounted on top of them are mounted on truly empty\ndirectories.  Given that some directories can gain entries over time,\nknowing that a directory is empty right now is insufficient.\n\nTherefore add supporting infrastructure for permantently empty\ndirectories that proc and sysfs can use when they create mount points\nfor filesystems and fs_fully_visible can use to test for permanently\nempty directories to ensure that nothing will be gained by mounting a\nfresh copy of proc or sysfs.\n\nSigned-off-by: \"Eric W. Biederman\" <ebiederm@xmission.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/NigelCunningham/tuxonice-kernel/commits/bb9fcac1598aeecc9079c467850b01e1c2515124"},{"sha":"4419466202070be255b8b0214f0f151c33c59ed6","author":{"email":"8a741aa8cbd77ebc4a56ddb528ce9fd15d42f034@xmission.com","name":"Eric W. Biederman"},"message":"sysctl: Allow creating permanently empty directories that serve as mountpoints.\n\ncommit f9bd6733d3f11e24f3949becf277507d422ee1eb upstream.\n\nAdd a magic sysctl table sysctl_mount_point that when used to\ncreate a directory forces that directory to be permanently empty.\n\nUpdate the code to use make_empty_dir_inode when accessing permanently\nempty directories.\n\nUpdate the code to not allow adding to permanently empty directories.\n\nUpdate /proc/sys/fs/binfmt_misc to be a permanently empty directory.\n\nSigned-off-by: \"Eric W. Biederman\" <ebiederm@xmission.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/NigelCunningham/tuxonice-kernel/commits/4419466202070be255b8b0214f0f151c33c59ed6"},{"sha":"594c980a9aea06a8243e41a59c1adbb39b21c46b","author":{"email":"8a741aa8cbd77ebc4a56ddb528ce9fd15d42f034@xmission.com","name":"Eric W. Biederman"},"message":"proc: Allow creating permanently empty directories that serve as mount points\n\ncommit eb6d38d5427b3ad42f5268da0f1dd31bb0af1264 upstream.\n\nAdd a new function proc_create_mount_point that when used to creates a\ndirectory that can not be added to.\n\nAdd a new function is_empty_pde to test if a function is a mount\npoint.\n\nUpdate the code to use make_empty_dir_inode when reporting\na permanently empty directory to the vfs.\n\nUpdate the code to not allow adding to permanently empty directories.\n\nUpdate /proc/openprom and /proc/fs/nfsd to be permanently empty directories.\n\nSigned-off-by: \"Eric W. Biederman\" <ebiederm@xmission.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/NigelCunningham/tuxonice-kernel/commits/594c980a9aea06a8243e41a59c1adbb39b21c46b"},{"sha":"b6a80c2dd807e4f6a18d914b1731b8253a8c0728","author":{"email":"8a741aa8cbd77ebc4a56ddb528ce9fd15d42f034@xmission.com","name":"Eric W. Biederman"},"message":"kernfs: Add support for always empty directories.\n\ncommit ea015218f2f7ace2dad9cedd21ed95bdba2886d7 upstream.\n\nAdd a new function kernfs_create_empty_dir that can be used to create\ndirectory that can not be modified.\n\nUpdate the code to use make_empty_dir_inode when reporting a\npermanently empty directory to the vfs.\n\nUpdate the code to not allow adding to permanently empty directories.\n\nSigned-off-by: \"Eric W. Biederman\" <ebiederm@xmission.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/NigelCunningham/tuxonice-kernel/commits/b6a80c2dd807e4f6a18d914b1731b8253a8c0728"},{"sha":"1ada60429f016e4a275dfc4dae112ccd0bfa1da6","author":{"email":"8a741aa8cbd77ebc4a56ddb528ce9fd15d42f034@xmission.com","name":"Eric W. Biederman"},"message":"sysfs: Add support for permanently empty directories to serve as mount points.\n\ncommit 87d2846fcf88113fae2341da1ca9a71f0d916f2c upstream.\n\nAdd two functions sysfs_create_mount_point and\nsysfs_remove_mount_point that hang a permanently empty directory off\nof a kobject or remove a permanently emptpy directory hanging from a\nkobject.  Export these new functions so modular filesystems can use\nthem.\n\nAcked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: \"Eric W. Biederman\" <ebiederm@xmission.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/NigelCunningham/tuxonice-kernel/commits/1ada60429f016e4a275dfc4dae112ccd0bfa1da6"},{"sha":"04d3e95c9c807d45ee413b5cd83d0a6b5c24af41","author":{"email":"8a741aa8cbd77ebc4a56ddb528ce9fd15d42f034@xmission.com","name":"Eric W. Biederman"},"message":"mnt: Update fs_fully_visible to test for permanently empty directories\n\ncommit 7236c85e1be51a9e25ba0f6e087a66ca89605a49 upstream.\n\nfs_fully_visible attempts to make fresh mounts of proc and sysfs give\nthe mounter no more access to proc and sysfs than if they could have\nby creating a bind mount.  One aspect of proc and sysfs that makes\nthis particularly tricky is that there are other filesystems that\ntypically mount on top of proc and sysfs.  As those filesystems are\nmounted on empty directories in practice it is safe to ignore them.\nHowever testing to ensure filesystems are mounted on empty directories\nhas not been something the in kernel data structures have supported so\nthe current test for an empty directory which checks to see\nif nlink <= 2 is a bit lacking.\n\nproc and sysfs have recently been modified to use the new empty_dir\ninfrastructure to create all of their dedicated mount points.  Instead\nof testing for S_ISDIR(inode->i_mode) && i_nlink <= 2 to see if a\ndirectory is empty, test for is_empty_dir_inode(inode).  That small\nchange guaranteess mounts found on proc and sysfs really are safe to\nignore, because the directories are not only empty but nothing can\never be added to them.  This guarantees there is nothing to worry\nabout when mounting proc and sysfs.\n\nSigned-off-by: \"Eric W. Biederman\" <ebiederm@xmission.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/NigelCunningham/tuxonice-kernel/commits/04d3e95c9c807d45ee413b5cd83d0a6b5c24af41"},{"sha":"28c79884a1f67811117048ce4c11c9a2ff995c73","author":{"email":"8a741aa8cbd77ebc4a56ddb528ce9fd15d42f034@xmission.com","name":"Eric W. Biederman"},"message":"mnt: Refactor the logic for mounting sysfs and proc in a user namespace\n\ncommit 1b852bceb0d111e510d1a15826ecc4a19358d512 upstream.\n\nFresh mounts of proc and sysfs are a very special case that works very\nmuch like a bind mount.  Unfortunately the current structure can not\npreserve the MNT_LOCK... mount flags.  Therefore refactor the logic\ninto a form that can be modified to preserve those lock bits.\n\nAdd a new filesystem flag FS_USERNS_VISIBLE that requires some mount\nof the filesystem be fully visible in the current mount namespace,\nbefore the filesystem may be mounted.\n\nMove the logic for calling fs_fully_visible from proc and sysfs into\nfs/namespace.c where it has greater access to mount namespace state.\n\nSigned-off-by: \"Eric W. Biederman\" <ebiederm@xmission.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/NigelCunningham/tuxonice-kernel/commits/28c79884a1f67811117048ce4c11c9a2ff995c73"},{"sha":"755ff2b4fcdb5ef50b4ee48b70f0d8dd22643971","author":{"email":"8a741aa8cbd77ebc4a56ddb528ce9fd15d42f034@xmission.com","name":"Eric W. Biederman"},"message":"mnt: Modify fs_fully_visible to deal with locked ro nodev and atime\n\ncommit 8c6cf9cc829fcd0b179b59f7fe288941d0e31108 upstream.\n\nIgnore an existing mount if the locked readonly, nodev or atime\nattributes are less permissive than the desired attributes\nof the new mount.\n\nOn success ensure the new mount locks all of the same readonly, nodev and\natime attributes as the old mount.\n\nThe nosuid and noexec attributes are not checked here as this change\nis destined for stable and enforcing those attributes causes a\nregression in lxc and libvirt-lxc where those applications will not\nstart and there are no known executables on sysfs or proc and no known\nway to create exectuables without code modifications\n\nFixes: e51db73532955 (\"userns: Better restrictions on when proc and sysfs can be mounted\")\nSigned-off-by: \"Eric W. Biederman\" <ebiederm@xmission.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/NigelCunningham/tuxonice-kernel/commits/755ff2b4fcdb5ef50b4ee48b70f0d8dd22643971"},{"sha":"ab873f188eeb7077fa6e904f22d63e4350bb02ed","author":{"email":"8a741aa8cbd77ebc4a56ddb528ce9fd15d42f034@xmission.com","name":"Eric W. Biederman"},"message":"sysfs: Create mountpoints with sysfs_create_mount_point\n\ncommit f9bb48825a6b5d02f4cabcc78967c75db903dcdc upstream.\n\nThis allows for better documentation in the code and\nit allows for a simpler and fully correct version of\nfs_fully_visible to be written.\n\nThe mount points converted and their filesystems are:\n/sys/hypervisor/s390/       s390_hypfs\n/sys/kernel/config/         configfs\n/sys/kernel/debug/          debugfs\n/sys/firmware/efi/efivars/  efivarfs\n/sys/fs/fuse/connections/   fusectl\n/sys/fs/pstore/             pstore\n/sys/kernel/tracing/        tracefs\n/sys/fs/cgroup/             cgroup\n/sys/kernel/security/       securityfs\n/sys/fs/selinux/            selinuxfs\n/sys/fs/smackfs/            smackfs\n\nAcked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: \"Eric W. Biederman\" <ebiederm@xmission.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/NigelCunningham/tuxonice-kernel/commits/ab873f188eeb7077fa6e904f22d63e4350bb02ed"},{"sha":"aeb2017c1f5d02e4bb636f7db211612baa7fc0f2","author":{"email":"e835aaae27ef45c770cbc83733586d01aadc3a43@intel.com","name":"Aaron Lu"},"message":"gpio: crystalcove: set IRQCHIP_SKIP_SET_WAKE for the irqchip\n\ncommit 61e749d7e1627d375156553ea0ae83c4f6bb5a9b upstream.\n\nThe CrystalCove GPIO irqchip doesn't have irq_set_wake callback defined\nso we should set IRQCHIP_SKIP_SET_WAKE for it or it would cause an irq\ndesc's wake_depth unbalanced warning during system resume phase from the\ngpio_keys driver, which is the driver for the power button of the ASUS\nT100 laptop.\n\nSigned-off-by: Aaron Lu <aaron.lu@intel.com>\nSigned-off-by: Linus Walleij <linus.walleij@linaro.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/NigelCunningham/tuxonice-kernel/commits/aeb2017c1f5d02e4bb636f7db211612baa7fc0f2"},{"sha":"ec187b8cc355fdbc889461392fcefdcffa2734a5","author":{"email":"1e0ce936bb9b355d257bf5790d2513c3f28be22b@linux.vnet.ibm.com","name":"Paul E. McKenney"},"message":"rcu: Correctly handle non-empty Tiny RCU callback list with none ready\n\ncommit 6e91f8cb138625be96070b778d9ba71ce520ea7e upstream.\n\nIf, at the time __rcu_process_callbacks() is invoked,  there are callbacks\nin Tiny RCU's callback list, but none of them are ready to be invoked,\nthe current list-management code will knit the non-ready callbacks out\nof the list.  This can result in hangs and possibly worse.  This commit\ntherefore inserts a check for there being no callbacks that can be\ninvoked immediately.\n\nThis bug is unlikely to occur -- you have to get a new callback between\nthe time rcu_sched_qs() or rcu_bh_qs() was called, but before we get to\n__rcu_process_callbacks().  It was detected by the addition of RCU-bh\ntesting to rcutorture, which in turn was instigated by Iftekhar Ahmed's\nmutation testing.  Although this bug was made much more likely by\n915e8a4fe45e (rcu: Remove fastpath from __rcu_process_callbacks()), this\ndid not cause the bug, but rather made it much more probable.   That\nsaid, it takes more than 40 hours of rcutorture testing, on average,\nfor this bug to appear, so this fix cannot be considered an emergency.\n\nSigned-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>\nReviewed-by: Josh Triplett <josh@joshtriplett.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/NigelCunningham/tuxonice-kernel/commits/ec187b8cc355fdbc889461392fcefdcffa2734a5"},{"sha":"94179c551d8f340967c3a5ccfda30a83a707d16b","author":{"email":"bf668d4b220231d97fe248d4ae0ba63a1d887e4c@linux.vnet.ibm.com","name":"Brian King"},"message":"ipr: Increase default adapter init stage change timeout\n\ncommit 45c44b5ff9caa743ed9c2bfd44307c536c9caf1e upstream.\n\nIncrease the default init stage change timeout from 15 seconds to 30 seconds.\nThis resolves issues we have seen with some adapters not transitioning\nto the first init stage within 15 seconds, which results in adapter\ninitialization failures.\n\nSigned-off-by: Brian King <brking@linux.vnet.ibm.com>\nSigned-off-by: James Bottomley <JBottomley@Odin.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/NigelCunningham/tuxonice-kernel/commits/94179c551d8f340967c3a5ccfda30a83a707d16b"},{"sha":"61278e7e35827c65337515016835712a4c6f4add","author":{"email":"214c418002e37328fa4269e3a4c952adc6e79ea4@icequake.net","name":"Ryan Underwood"},"message":"Disable write buffering on Toshiba ToPIC95\n\ncommit 2fb22a8042fe96b4220843f79241c116d90922c4 upstream.\n\nDisable write buffering on the Toshiba ToPIC95 if it is enabled by\nsomebody (it is not supposed to be a power-on default according to\nthe datasheet). On the ToPIC95, practically no 32-bit Cardbus card\nwill work under heavy load without locking up the whole system if\nthis is left enabled. I tried about a dozen. It does not affect\n16-bit cards. This is similar to the O2 bugs in early controller\nrevisions it seems.\n\nBugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=55961\nSigned-off-by: Ryan C. Underwood <nemesis@icequake.net>\nSigned-off-by: Dominik Brodowski <linux@dominikbrodowski.net>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/NigelCunningham/tuxonice-kernel/commits/61278e7e35827c65337515016835712a4c6f4add"},{"sha":"2b453f0386bda83fbc6ff176b3750a9b4aaf7fc0","author":{"email":"4596b3305151c7ee743192a95d394341e3d3b644@suse.de","name":"Takashi Iwai"},"message":"ALSA: pcm: Fix pcm_class sysfs output\n\ncommit 60b93030b44a8c2cd015cebe5624fd7552ec67ec upstream.\n\nThe pcm_class sysfs of each PCM substream gives only \"none\" since the\nrecent code change to embed the struct device.  Fix the code to point\ndirectly to the embedded device object properly.\n\nFixes: ef46c7af93f9 ('ALSA: pcm: Embed struct device')\nSigned-off-by: Takashi Iwai <tiwai@suse.de>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/NigelCunningham/tuxonice-kernel/commits/2b453f0386bda83fbc6ff176b3750a9b4aaf7fc0"},{"sha":"5b8997cb84ba0ec88eb5e28ef7531767566c009a","author":{"email":"9fb354e0a5603a0331399c18f4aa5aab2f9d9c5b@canonical.com","name":"David Henningsson"},"message":"ALSA: hda - Fix Dock Headphone on Thinkpad X250 seen as a Line Out\n\ncommit ec56af67a10a0d82b79027878a81fce08d002d50 upstream.\n\nThinkpad X250, when attached to a dock, has two headphone outs but\nno line out. Make sure we don't try to turn this into one headphone\nand one line out (since that disables the headphone amp on the dock).\n\nAlsa-info at http://www.alsa-project.org/db/?f=36f8764e1d782397928feec715d0ef90dfddd4c1\n\nSigned-off-by: David Henningsson <david.henningsson@canonical.com>\nSigned-off-by: Takashi Iwai <tiwai@suse.de>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/NigelCunningham/tuxonice-kernel/commits/5b8997cb84ba0ec88eb5e28ef7531767566c009a"},{"sha":"8227ae83eb27986b8155d87fa9e161edbd8c171f","author":{"email":"08dc22c6156113f2deff178e35e3ed9b24d6af9e@amd.com","name":"Alex Deucher"},"message":"ALSA: hda - set proper caps for newer AMD hda audio in KB/KV\n\ncommit 650474fb737c3e0ea0f6ab8e43c2cd161080ce5c upstream.\n\nFixes audio problems on newer asics.\n\nNoticed by: Kelly Anderson <kelly@xilka.com>\nSigned-off-by: Alex Deucher <alexander.deucher@amd.com>\nSigned-off-by: Takashi Iwai <tiwai@suse.de>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/NigelCunningham/tuxonice-kernel/commits/8227ae83eb27986b8155d87fa9e161edbd8c171f"},{"sha":"a17a9a151abdcb3d3c35e819fe7ccf70bb30c847","author":{"email":"4596b3305151c7ee743192a95d394341e3d3b644@suse.de","name":"Takashi Iwai"},"message":"ALSA: hda - Add headset support to Acer Aspire V5\n\ncommit 7819717b11346b8a5420b223b46600e394049c66 upstream.\n\nAcer Aspire V5 with ALC282 codec needs the similar quirk like Dell\nlaptops to support the headset mic.  The headset mic pin is 0x19 and\nit's not exposed by BIOS, thus we need to fix the pincfg as well.\n\nBugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=96201\nSigned-off-by: Takashi Iwai <tiwai@suse.de>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/NigelCunningham/tuxonice-kernel/commits/a17a9a151abdcb3d3c35e819fe7ccf70bb30c847"},{"sha":"28bbb25f4ce63f6a152734a74d14c5038b2191a6","author":{"email":"4596b3305151c7ee743192a95d394341e3d3b644@suse.de","name":"Takashi Iwai"},"message":"ALSA: hda - Fix the dock headphone output on Fujitsu Lifebook E780\n\ncommit 4df3fd1700abbb53bd874143dfd1f9ac9e7cbf4b upstream.\n\nFujitsu Lifebook E780 sets the sequence number 0x0f to only only of\nthe two headphones, thus the driver tries to assign another as the\nline-out, and this results in the inconsistent mapping between the\ncreated jack ctl and the actual I/O.  Due to this, PulseAudio doesn't\nhandle it properly and gets the silent output.\n\nThe fix is to ignore the non-HP sequencer checks.\n\nBugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=99681\nSigned-off-by: Takashi Iwai <tiwai@suse.de>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/NigelCunningham/tuxonice-kernel/commits/28bbb25f4ce63f6a152734a74d14c5038b2191a6"},{"sha":"8ce84317f1bd73c9e5d10a1cc7f8ff5a6ae86106","author":{"email":"27ffc44a8ec6a212fba98cfc3246c6ce8ab131e0@intel.com","name":"Rafael J. Wysocki"},"message":"ACPI / init: Switch over platform to the ACPI mode later\n\ncommit b064a8fa77dfead647564c46ac8fc5b13bd1ab73 upstream.\n\nCommit 73f7d1ca3263 \"ACPI / init: Run acpi_early_init() before\ntimekeeping_init()\" moved the ACPI subsystem initialization,\nincluding the ACPI mode enabling, to an earlier point in the\ninitialization sequence, to allow the timekeeping subsystem\nuse ACPI early.  Unfortunately, that resulted in boot regressions\non some systems and the early ACPI initialization was moved toward\nits original position in the kernel initialization code by commit\nc4e1acbb35e4 \"ACPI / init: Invoke early ACPI initialization later\".\n\nHowever, that turns out to be insufficient, as boot is still broken\non the Tyan S8812 mainboard.\n\nTo fix that issue, split the ACPI early initialization code into\ntwo pieces so the majority of it still located in acpi_early_init()\nand the part switching over the platform into the ACPI mode goes into\na new function, acpi_subsystem_init(), executed at the original early\nACPI initialization spot.\n\nThat fixes the Tyan S8812 boot problem, but still allows ACPI\ntables to be loaded earlier which is useful to the EFI code in\nefi_enter_virtual_mode().\n\nLink: https://bugzilla.kernel.org/show_bug.cgi?id=97141\nFixes: 73f7d1ca3263 \"ACPI / init: Run acpi_early_init() before timekeeping_init()\"\nReported-and-tested-by: Marius Tolzmann <tolzmann@molgen.mpg.de>\nSigned-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>\nAcked-by: Toshi Kani <toshi.kani@hp.com>\nReviewed-by: Hanjun Guo <hanjun.guo@linaro.org>\nReviewed-by: Lee, Chun-Yi <jlee@suse.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/NigelCunningham/tuxonice-kernel/commits/8ce84317f1bd73c9e5d10a1cc7f8ff5a6ae86106"},{"sha":"f52eca0d7843d0b5b157b59b26ebec827bef4a9f","author":{"email":"27ffc44a8ec6a212fba98cfc3246c6ce8ab131e0@intel.com","name":"Rafael J. Wysocki"},"message":"ACPI / PM: Add missing pm_generic_complete() invocation\n\ncommit 3d56402d3fa8d10749eeb36293dd1992bd5ad0c3 upstream.\n\nAdd missing invocation of pm_generic_complete() to\nacpi_subsys_complete() to allow ->complete callbacks provided\nby the drivers of devices using the ACPI PM domain to be executed\nduring system resume.\n\nFixes: f25c0ae2b4c4 (ACPI / PM: Avoid resuming devices in ACPI PM domain during system suspend)\nSigned-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/NigelCunningham/tuxonice-kernel/commits/f52eca0d7843d0b5b157b59b26ebec827bef4a9f"}]}