SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I built Linux 5.2 on both my distros last night (slackware-current and Manjaro). Lots of new settings to say "N" to :-)
So far, so good on my hardware. I'm sure there will be dire looking things in the changelogs that keep me upgrading to every point release for a while, though.
VirtualBox 6.0.8 still compiles its host modules for Linux 5.2 (I don't have any Linux guests at this time so I wouldn't know about the guest additions)
I built Linux 5.2 on both my distros last night (slackware-current and Manjaro). Lots of new settings to say "N" to :-)
Darn, I was hoping to claim bragging rights. All is well here as well. I usually answer 'm' or 'y' unless I can see a good reason why not, which is why I have lots of modules complied that I will never use. One thing that confused me, if I can tie my memory of make oldconfig with the quick look I had with make menuconfig was the new kernel hardening - memory initialization settings. I could not find anything on this by googling, but it seemed like it might be a good idea. So I winged it and picked the least impact option that was not 'off'.
I build my kernels for performance (I honestly don't give a shit about security on my desktop systems... sue me :-) so I disable such things and the CPU mitigations. I said a more emphatic no to those newer ones, because I'd rather not use gcc plugins. Poisoning the stack after syscalls doesn't sound like a performance enhancing feature either.
I'd change my tune if it was important (for example I don't neglect security on servers)
And all I need to do to get a case-insensitive directory are a mkdir and a chattr?
I'm going to have to build a 5.2 kernel (and, if necessary, a new e2fsprogs) to play Quake with.
There are a number of games (Fallout, Baldur's Gate, Alpha Centauri, Quake, etc) whose mods expect a case-insensitive filesystem even when they're running in Linux (either natively or in WINE).
Just tried.
Code:
bash-5.0# mkdir a
bash-5.0# chattr +F a
chattr: Operation not supported while setting flags on a
I created the filesystem in mid May, and I assume it's not working for me because it doesn't have the casefold feature.
How to add it?
As far as I can tell, it's by adding the "encoding" extended attribute when creating the filesystem.
bash-5.0# fallocate -l 512M image.img
bash-5.0# mkfs -t ext4 -E encoding=utf8 image.img
mke2fs 1.45.2 (27-May-2019)
64-bit filesystem support is not enabled. The larger fields afforded by this feature enable full-strength checksumming. Pass -O 64bit to rectify.
Discarding device blocks: done
Creating filesystem with 131072 4k blocks and 32768 inodes
Filesystem UUID: b0c63909
bash-5.0# mount image.img a
mount: /root/a: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error.
bash-5.0# dmesg -T | tail -n 1
[Wed Jul 10 07:02:29 2019] EXT4-fs (loop0): Filesystem with casefold feature cannot be mounted without CONFIG_UNICODE
And... I see this in "make menuconfig", under "File Systems":
Code:
[ ] UTF-8 normalization and casefolding support
Pretty good idea of what I need to try next. Will do it later.
Egads some of the bugs fixed in 4.4.185 look bad, especially the memory paging one (second patch from the bottom of the changelog). Worthwhile fixes for alsa, crypto, bluetooth, ipv4 too.
I have a changelog summarizer script half-written. Need to finish it so finding the important bits is easier.
Pretty good idea of what I need to try next. Will do it later.
I rebuilt a 5.2.0 kernel with CONFIG_UNICODE (which resulted in the entire kernel being rebuilt), and yes it worked!
Code:
bash-5.0# fallocate -l 512M test.img
bash-5.0# mkfs -t ext4 -E encoding=utf8 test.img
mke2fs 1.45.2 (27-May-2019)
64-bit filesystem support is not enabled. The larger fields afforded by this feature enable full-strength checksumming. Pass -O 64bit to rectify.
Discarding device blocks: done
Creating filesystem with 131072 4k blocks and 32768 inodes
Filesystem UUID: 76ea8851-aa79-43bf-8bef-264304af9ecd
Superblock backups stored on blocks:
32768, 98304
Allocating group tables: done
Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done
bash-5.0# mkdir test
bash-5.0# mount test.img test
bash-5.0# cd test
bash-5.0# mkdir dos
bash-5.0# chattr +F dos
bash-5.0# cd dos
bash-5.0# touch a.txt
bash-5.0# touch A.txt
bash-5.0# ls
a.txt
bash-5.0# mkdir b
bash-5.0# touch b/a.txt
bash-5.0# touch b/A.txt
bash-5.0# ls b
a.txt
If you don't want to click through the reply links to see what this is about:
I created an ext4 filesystem with casefold support, mounted it, and created a directory in it called "dos". I then made that directory case-insensitive by running "chattr +F" on it.
The rest is testing that the case-insensitivity worked.
mwifiex_update_bss_desc_with_ie() calls memcpy() unconditionally in
a couple places without checking the destination size. Since the
source is given from user-space, this may trigger a heap buffer
overflow.
Fix it by putting the length check before performing memcpy().
This fix addresses CVE-2019-3846.
Last edited by mats_b_tegner; 07-14-2019 at 07:00 AM.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,085
Original Poster
Rep:
Quote:
Originally Posted by ehartman
Unfortunately they didn't work, the 32-bit kernel has stuck at 4.4.184 and the 64-bit at 4.4.182, so no changes.
Yes, usually I check once or twice a day and noticed it didn't work the last time around.
I really hope Dave is OK.
Does anyone know if something has happened to him or did he simply get tried of maintaining the scripts?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.