REQUEST: modularize packet socket
by George Karakougioumtzis
Hello. Since fedora aims to be one of the most secure distros, i think
packet socket support should be configured and compiled as a module.
Therefore one that needs to use nmap,tcpdump,wireshark and other
sniffing tools will still be able to do so but another who doesn't want
to will be able to blacklist the module. Just a thought but i would
appreciate a reply. Thanks.
10 years, 1 month
Preparing Change Proposal: Modular Kernel Packaging for Cloud - Feedback?
by Sandro "red" Mathys
In the past ~24h, I've been preparing the "Modular Kernel Packaging
for Cloud" change. Before I submit it to the wrangler, I'm looking for
everyone's feedback. Note this is my first change proposal so I might
have misunderstood things or whatever.
https://fedoraproject.org/wiki/Changes/Modular_Kernel_Packaging_for_Cloud
Note, that I haven't yet reached out to the Anaconda team (regarding
the possibility to install kernel-core instead of kernel) but will do
so now. They don't seem critical to the change, though but just to the
way we're implementing it when creating the images. (Assuming we will
use Anaconda to build F21 images).
Thanks,
Sandro
10 years, 1 month
Modular Kernel Packaging for Cloud
by Sandro "red" Mathys
Heads-up: I've taken ownership over the Cloud SIG's planned
"Cloud-Friendly Kernel Packaging" (aka "Modular Kernel Packaging for
Cloud") Change [0].
(Sorry for cross-posting this on the kernel and cloud lists, but both
the kernel team and the cloud SIG need to be involved in this
discussion).
Obviously, we wish for modular kernel packaging and Josh Boyer already
reached out to the cloud SIG in this regard a while ago when we didn't
really know what we want yet [1]. We do now know that somewhat better
[2] but details could still require additional discussion. Our
motivation is to save space, time and bandwidth (the latter two
referring to required updates) as in the cloud, all three equal to
costs. And yes, we also target things other than the kernel to save
space.
So, in our case hardware drivers are rather unnecessary and the kernel
experts might know other ways to shrink the footprint for our limited
use cases. The kernel we require supports all primary architectures
(i686 and x86_64 right now, ARM likely later) and is able to run on a
hypervisor (primarily KVM and Xen but support for ESXi and Hyper-V are
becoming crucial in private clouds). Only. No bare-metal. We also
require support for Linux Containers (LXC) to enable the use of
Docker.
Now, I heard some people screaming when I said HW drivers are
unnecessary. Some people will want to make use of PCI passthrough and
while I think we don't want to ship the necessary modules by default,
they should be easily installable through a separate package. If some
more granularity is acceptable (and makes sense), I think one package
for SRIOV NICs, one for graphic cards (to enable mathematical
computation stuff) and one for everything else PCI passthrough (plus
one for all other HW drivers for the non-cloud products) would be
totally nice.
What does everybody think about this? Can it be done? How is it best
done? What's the timeframe (we'd really like to see this implemented
in F21 Beta but obviously the earlier modular kernels can be tested,
the better)? Do you require additional input?
Please try to keep the discussion as simple as possible (in terms of
us non-kernel hackers should be able to follow it). Just like Josh
requested when reaching out to us: "Explain it to me like I'm a
child."
Thanks,
Sandro
[0] https://fedoraproject.org/wiki/Cloud_Changelist#Change:_Cloud-Friendly_Ke...
[1] https://lists.fedoraproject.org/pipermail/cloud/2013-October/002862.html
[2] https://fedoraproject.org/wiki/Cloud_PRD
10 years, 1 month
cloud / zram
by Reindl Harald
in case of cloud / virtualization i wonder what is the
state of "zram" in the Fedora Kernel, zswap is available
and can be enabled with "zswap.enabled=1" as boot paran
but zswap is more for a overcommited host to avoid disk paging
zram IMHO would be interesting for the guest systems and
both combined may lead to run *a lot* of more virtual
machines on the same host
____________________________________________________________
[root@srv-rhsoft:~]$ cat /boot/config-3.13.6-200.fc20.x86_64 | grep -i zswap
CONFIG_ZSWAP=y
[root@srv-rhsoft:~]$ cat /boot/config-3.13.6-200.fc20.x86_64 | grep -i zram
[root@srv-rhsoft:~]$ locate zram
/usr/src/kernels/3.13.6-200.fc20.x86_64/drivers/staging/zram
/usr/src/kernels/3.13.6-200.fc20.x86_64/drivers/staging/zram/Kconfig
/usr/src/kernels/3.13.6-200.fc20.x86_64/drivers/staging/zram/Makefile
10 years, 1 month
Bluetooth virtual HCI driver ver 1.3
by poma
3.13.0-0.rc7.git2.2.fc21.x86_64:
depmod: ERROR: Module 'hci_vhci' has devname (vhci) but lacks major and
minor information. Ignoring.
poma
10 years, 1 month
[PATCH v2] [RESEND] Enable USB gadget subsystem outside ARM
by Lubomir Rintel
It's generally useful. On other architectures the UDC capable hardware might
not be very common, but the dummy HCD makes it possible to use such hardware
for development and emulation of USB gadget driver code.
---
Changes since v2:
* Rebased on v3.14-rc4-45-gd2a0476 (fedora package git: 2323b0271)
* Do not move the modules to modules-extra
According to Peter & Adam, even certain Intel hardware has device mode
capability, so this certainly is useful.
config-armv7-generic | 58 -------------------------------------------------
config-debug | 5 +++++
config-generic | 61 ++++++++++++++++++++++++++++++++++++++++++++++++----
config-nodebug | 3 +++
4 files changed, 65 insertions(+), 62 deletions(-)
diff --git a/config-armv7-generic b/config-armv7-generic
index a81ca01..d71e105 100644
--- a/config-armv7-generic
+++ b/config-armv7-generic
@@ -194,64 +194,6 @@ CONFIG_AX88796_93CX6=y
CONFIG_USB_ISP1760_HCD=m
# CONFIG_USB_EHCI_HCD_ORION is not set
-# usb gadget
-CONFIG_USB_GADGET=m
-CONFIG_USB_GADGET_MUSB_HDRC=m
-CONFIG_USB_GADGET_VBUS_DRAW=100
-CONFIG_USB_GADGET_STORAGE_NUM_BUFFERS=2
-CONFIG_USB_MUSB_HDRC=m
-CONFIG_USB_MUSB_DUAL_ROLE=y
-CONFIG_USB_MUSB_DSPS=m
-CONFIG_USB_GPIO_VBUS=m
-CONFIG_USB_G_ACM_MS=m
-CONFIG_USB_G_DBGP=m
-CONFIG_USB_G_DBGP_PRINTK=y
-CONFIG_USB_G_DBGP_SERIAL=y
-CONFIG_USB_G_MULTI=m
-CONFIG_USB_G_MULTI_CDC=y
-# CONFIG_USB_G_MULTI_RNDIS is not set
-CONFIG_USB_G_NCM=m
-CONFIG_USB_G_SERIAL=m
-CONFIG_USB_ETH_EEM=y
-# CONFIG_USB_ETH_RNDIS is not set
-CONFIG_USB_CDC_COMPOSITE=m
-CONFIG_USB_GADGET_TARGET=m
-CONFIG_USB_MASS_STORAGE=m
-CONFIG_USB_CONFIGFS=m
-CONFIG_USB_CONFIGFS_ACM=y
-CONFIG_USB_CONFIGFS_ECM=y
-CONFIG_USB_CONFIGFS_ECM_SUBSET=y
-CONFIG_USB_CONFIGFS_EEM=y
-CONFIG_USB_CONFIGFS_MASS_STORAGE=y
-CONFIG_USB_CONFIGFS_NCM=y
-CONFIG_USB_CONFIGFS_OBEX=y
-# CONFIG_USB_CONFIGFS_RNDIS is not set
-CONFIG_USB_CONFIGFS_SERIAL=y
-CONFIG_USB_CONFIGFS_STORAGE=y
-# CONFIG_USB_CONFIGFS_F_LB_SS is not set
-# CONFIG_USB_CONFIGFS_F_FS is not set
-
-# CONFIG_MUSB_PIO_ONLY is not set
-# CONFIG_USB_MUSB_DEBUG is not set
-# CONFIG_USB_GADGET_DEBUG is not set
-# CONFIG_USB_GADGET_DEBUG_FILES is not set
-# CONFIG_USB_GADGET_DEBUG_FS is not set
-# CONFIG_USB_FUSB300 is not set
-# CONFIG_USB_RENESAS_USBHS is not set
-# CONFIG_USB_FOTG210_UDC is not set
-# CONFIG_USB_R8A66597 is not set
-# CONFIG_USB_PXA27X is not set
-# CONFIG_USB_MV_UDC is not set
-# CONFIG_USB_MV_U3D is not set
-# CONFIG_USB_M66592 is not set
-# CONFIG_USB_AMD5536UDC is not set
-# CONFIG_USB_NET2272 is not set
-# CONFIG_USB_NET2280 is not set
-# CONFIG_USB_GOKU is not set
-# CONFIG_USB_EG20T is not set
-# CONFIG_USB_DUMMY_HCD is not set
-# CONFIG_USB_ZERO_HNPTEST is not set
-
# Multifunction Devices
CONFIG_MFD_TPS65090=y
CONFIG_MFD_TPS65217=y
diff --git a/config-debug b/config-debug
index e225326..dfaacdb 100644
--- a/config-debug
+++ b/config-debug
@@ -124,3 +124,8 @@ CONFIG_EDAC_DEBUG=y
CONFIG_X86_DEBUG_STATIC_CPU_HAS=y
CONFIG_LATENCYTOP=y
CONFIG_SCHEDSTATS=y
+
+CONFIG_USB_GADGET_DEBUG=y
+CONFIG_USB_GADGET_DEBUG_FILES=y
+CONFIG_USB_GADGET_DEBUG_FS=y
+CONFIG_USB_GADGET_VERBOSE=y
diff --git a/config-generic b/config-generic
index fd1351d..cce441f 100644
--- a/config-generic
+++ b/config-generic
@@ -3714,7 +3714,6 @@ CONFIG_USB_ARMLINUX=y
CONFIG_USB_EPSON2888=y
CONFIG_USB_KC2190=y
-# CONFIG_USB_MUSB_HDRC is not set
# CONFIG_USB_CHIPIDEA is not set
#
@@ -3806,7 +3805,6 @@ CONFIG_USB_EZUSB=y
CONFIG_USB_EMI62=m
CONFIG_USB_LED=m
# CONFIG_USB_CYPRESS_CY7C63 is not set
-CONFIG_USB_G_SERIAL=m
#
# USB Miscellaneous drivers
@@ -3842,9 +3840,64 @@ CONFIG_USB_ETH=m
CONFIG_USB_FTDI_ELAN=m
CONFIG_USB_FILE_STORAGE=m
# CONFIG_USB_FILE_STORAGE_TEST is not set
-# CONFIG_USB_GADGET is not set
+
+# usb gadget
+CONFIG_USB_GADGET=m
+CONFIG_USB_GADGET_MUSB_HDRC=m
+CONFIG_USB_GADGET_VBUS_DRAW=100
+CONFIG_USB_GADGET_STORAGE_NUM_BUFFERS=2
+CONFIG_USB_MUSB_HDRC=m
+CONFIG_USB_MUSB_DUAL_ROLE=y
+CONFIG_USB_MUSB_DSPS=m
+CONFIG_USB_G_ACM_MS=m
+CONFIG_USB_G_DBGP=m
+CONFIG_USB_G_DBGP_SERIAL=y
+CONFIG_USB_G_MULTI=m
+CONFIG_USB_G_MULTI_CDC=y
+# CONFIG_USB_G_MULTI_RNDIS is not set
+CONFIG_USB_G_NCM=m
+CONFIG_USB_G_SERIAL=m
+CONFIG_USB_ETH_EEM=y
+# CONFIG_USB_ETH_RNDIS is not set
+CONFIG_USB_CDC_COMPOSITE=m
+CONFIG_USB_GADGET_TARGET=m
+CONFIG_USB_MASS_STORAGE=m
+CONFIG_USB_CONFIGFS=m
+CONFIG_USB_CONFIGFS_ACM=y
+CONFIG_USB_CONFIGFS_ECM=y
+CONFIG_USB_CONFIGFS_ECM_SUBSET=y
+CONFIG_USB_CONFIGFS_EEM=y
+CONFIG_USB_CONFIGFS_MASS_STORAGE=y
+CONFIG_USB_CONFIGFS_NCM=y
+CONFIG_USB_CONFIGFS_OBEX=y
+# CONFIG_USB_CONFIGFS_RNDIS is not set
+CONFIG_USB_CONFIGFS_SERIAL=y
+CONFIG_USB_CONFIGFS_STORAGE=y
+# CONFIG_USB_CONFIGFS_F_LB_SS is not set
+# CONFIG_USB_CONFIGFS_F_FS is not set
+
+# CONFIG_USB_RENESAS_USBHS is not set
+# CONFIG_USB_FOTG210_UDC is not set
+# CONFIG_USB_R8A66597 is not set
+# CONFIG_USB_PXA27X is not set
+# CONFIG_USB_MV_UDC is not set
+# CONFIG_USB_MV_U3D is not set
+# CONFIG_USB_M66592 is not set
+# CONFIG_USB_NET2272 is not set
+# CONFIG_USB_ZERO_HNPTEST is not set
+# CONFIG_USB_FUSB300 is not set
+# CONFIG_USB_AMD5536UDC is not set
+# CONFIG_USB_NET2280 is not set
+# CONFIG_USB_GOKU is not set
+# CONFIG_USB_EG20T is not set
+CONFIG_USB_DUMMY_HCD=m
+
# CONFIG_USB_DWC3 is not set
-# CONFIG_USB_GADGETFS is not set
+CONFIG_USB_GADGETFS=m
+CONFIG_USB_FUNCTIONFS=m
+CONFIG_USB_FUNCTIONFS_ETH=y
+# CONFIG_USB_FUNCTIONFS_RNDIS is not set
+CONFIG_USB_FUNCTIONFS_GENERIC=y
# CONFIG_USB_OXU210HP_HCD is not set
CONFIG_USB_IOWARRIOR=m
CONFIG_USB_ISIGHTFW=m
diff --git a/config-nodebug b/config-nodebug
index 9d4b2e9..dd9af68 100644
--- a/config-nodebug
+++ b/config-nodebug
@@ -128,3 +128,6 @@ CONFIG_X86_DEBUG_STATIC_CPU_HAS=y
# CONFIG_SCHEDSTATS is not set
# CONFIG_LATENCYTOP is not set
+# CONFIG_USB_GADGET_DEBUG is not set
+# CONFIG_USB_GADGET_DEBUG_FILES is not set
+# CONFIG_USB_GADGET_DEBUG_FS is not set
--
1.8.3.1
10 years, 1 month
kernel-tests master: skip stack-randomness on 32bit (8118a1e)
by Justin Forbes
Repository : http://git.fedorahosted.org/cgit/kernel-tests.git
On branch : master
>---------------------------------------------------------------
commit 8118a1e821c8613114f68ff3777857e380c8a353
Author: Justin M. Forbes <jforbes(a)redhat.com>
Date: Tue Mar 4 13:47:38 2014 -0600
skip stack-randomness on 32bit
>---------------------------------------------------------------
default/stack-randomness/runtest.sh | 9 ++++++++-
1 files changed, 8 insertions(+), 1 deletions(-)
diff --git a/default/stack-randomness/runtest.sh b/default/stack-randomness/runtest.sh
index 77d17de..4fa9b42 100755
--- a/default/stack-randomness/runtest.sh
+++ b/default/stack-randomness/runtest.sh
@@ -2,7 +2,14 @@
#
# Licensed under the terms of the GNU GPL License version 2
-COUNT=$(for i in `seq 1 1000` ; do grep stack /proc/self/maps; done | sort -u | uniq -c | wc -l)
+ARCH=$(uname -m)
+
+if [ "$ARCH" == "x86_64" ]; then
+ COUNT=$(for i in `seq 1 1000` ; do grep stack /proc/self/maps; done | sort -u | uniq -c | wc -l)
+else
+ exit 3
+fi
+
if [ $COUNT -lt 950 ]; then
echo "Stack randomness changes < 95% of the time ($COUNT)"
10 years, 1 month