similar to: [PATCH] initramfs: CPIO unpacking fix

The following patch unlinks (deletes) files, symlinks, FIFOs, devices etc before writing them when extracting CPIOs. It doesn't delete directories. This stops weird behaviour like: 1) writing through symlinks created in earlier CPIOs. eg foo->bar in the first CPIO. Having foo as a non link in a subsequent CPIO, results in bar being written and foo remaining as a symlink. 2)

According to "initramfs buffer format -- third draft" http://lwn.net/2002/0117/a/initramfs-buffer-format.php3 "the cpio "TRAILER!!!" entry (cpio end-of-archive) is optional, but is not ignored" The kernel handling does not follow this spec. If you add null padding after an uncompressed cpio without TRAILER!!! the kernel complains "no cpio magic". In a

hello! i'm using redhat 7.2 with ext3 as my primary fs on kernel 2.4.17 + grsecurity + acl after 2-3 days of uptime i'm expiriencing problems... i attached below excert from my system logs. machine stops responing for a few seconds and after then it looks, like it's in normal operation again. the only problem is load, which is incrementing constantly, but cpu is 99% idle... after

Hello everyone, Recently Nathan March reported on centos-virt list he's getting frequent Linux kernel crashes with Linux 4.9 LTS kernel because of the missing patch "tty: Fix ldisc crash on reopened tty". The patch was already merged upstream here: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=71472fa9c52b1da27663c275d416d8654b905f05 but then

We need an smb_mb() before waitqueue_active to avoid missing wakeups. Before Mitch was hitting a deadlock between the ordered flushers and the transaction commit because the ordered flushers were waiting for more refs and were never woken up, so those smp_mb()''s are the most important. Everything else I added for correctness sake and to avoid getting bitten by this again somewhere else.

I've had a long-standing problem syncing my home directory from one Linux system (RH Linux 7.3) to another (RH Linux 9). I am now running rsync version 2.6.2 on both ends. I use ssh as the data transport. The two machines are separated by a VPN over the Internet. What happens is that the sending rsync just appears to hang. The receiving rsync processes are no longer running when I go

Hello, There seems to be problem in the cpio unpack in the kernel in initramfs. I have an empty "/sys" directory in my cpio archive, but it never shows up in my extracted initramfs. I've confirmed that extracting the archive again with cpio results in a correct tree, but it doesn't appear on boot when extracted by the kernel. Any ideas? I poked a bit, but I haven't

Using fsdlm/ocfs2_controld.cman, I've rerun the test I've been having problems with on 2.6.30-rc1. After running for several minutes in the same directory on three nodes, the test hangs, and I collect the following information: bull-01 ------- 3053 S< [ocfs2dc] ocfs2_downconvert_thread 3054 S< [dlm_astd] dlm_astd 3055 S< [dlm_scand]

I've attached the .gz'ed log of another EXT3 crash on my PPC box. This time it was on IDE and I was doing a tab completion as it died. -- Tom Rini (TR1265) http://gate.crashing.org/~trini/

hello! i'm using redhat 7.2 with ext3 as my primary fs on kernel 2.4.17 + grsecurity + acl after 2-3 days of uptime i'm expiriencing problems... i attached below excert from my system logs. machine stops responing for a few seconds and after then it looks, like it's in normal operation again. the only problem is load, which is incrementing constantly, but cpu is 99% idle...

I''ve upgraded to linux 3.10 and enabled extended inode refs and skinny metadata extent refs with these commands: btrfstune -r /dev/sdc1 btrfstune -x /dev/sdc1 Since then, I have "WARNING: at fs/btrfs/backref.c:903 find_parent_nodes+0x616/0x815 [btrfs]()" showing up like crazy: # grep -c "WARNING: at fs/btrfs/backref.c:903" syslog 181819 That''s after just

[Mod: The to address has been changed. The original message has been CC'ed to linux-security. This is mostly FYI only -- alex] Winfried, Good question. Since Linux-2.2.* has hit the streets, I'm guessing there may be wider interest in this sort of thing so I'm CC'ing my reply to linux-security. The capability stuff in the kernel provides a way to strip away all of the privilege

Hi all, This is an alternative approach to atomic user transactions for btrfs. The old start/end ioctls suffer from some basic limitations, namely - We can''t properly reserve space ahead of time to avoid ENOSPC part way through the transaction, and - The process may die (seg fault, SIGKILL) part way through the transaction. Currently when that happens the partial transaction will

Hi, On Thu, Jan 24, 2002 at 04:54:34PM +0100, frode wrote: > > I got the following error while rm'ing a 700mb file from an ext3 partition: > > Assertion failure in journal_unmap_buffer() at transaction.c:1857: > "transaction == journal->j_running_transaction" Hmm --- this is not one I think I've ever seen before. > >>EIP; c015ea1a

Hello again, We have hit some performance problem today in one of our clusters. The performance suddenly drop from the normal performance (about 30Mbytes/s), read/write, to a few Kbytes/s (about 200Kbytes/s), read only, for a while, and as sudden as it started, it backs to the normal read/write performance, cycling randomly. When the "read only" occurs on one node, the other shows only

Hello I am on Athlon 1Gz, kernel 2.4.8. I was running a perl pgm with a lot of disk access, deletions and symlinks creations... Maybe It is due to the kernel version. Could you please inform me if must upgrade to a more recent kernel ? Thanks a lot the kernel logs are : in errors logs Oct 18 17:31:16 tadorne kernel: Assertion failure in journal_revoke_Rb5884a32() at revoke.c:307:

Hello, I was using a bunch of cpios in initramfs as a working system, and wondering why the unused files weren't being paged out to swap. So I reread ramfs-rootfs-initramfs.txt and now I know. So I wrote the attached utility. It creates a tmpfs, moves all files on the initramfs, moves / and executes the real init. It works, even with hardlinks, but it isn't the correct approach. Have

Hello, Over the last month or so, I've noticed the following error showing up repeatedly in my system logs under kernel 2.4.18-ac3 and more recently under 2.4.19-rc1: EXT3-fs error (device ide0(3,3)) in ext3_new_inode: error 28 I've now been able to capture the following Oops before the system went down entirely: Assertion failure in do_get_write_access() at transaction.c:611:

I'm not sure when exactly this started, but currently when I specify a ramfs image via the initrd line in grub, kinit picks it up as an initrd and tries (and fails) to unpack it and run linuxrc from it. I'm assuming this is not the intended behavior. Can anyone point me into the proper direction for unpacking an initramfs image ontop of the in-kernel image? Currently, I am using kernel

Hey, I am trying to open a win32 VSTi which installed fine on a fresh install of wine 1.1.15 (debian sid, dell latitude laptop, intel board, pentium M). The audio environment is fine (jack, ALSA) and other VSTis work nicely. But this one does not, it craps out the error message "Error while unpacking program, code LP5". I googled this error msg on the net, and most of the time, it