Hello,
is it possible to build the kernel with the -fsanitize=safe-stack option?
I have tried make CC="clang -fsanitize=safe-stack" CXX="clang++
-fsanitize=safe-stack"
but it doesn't display any clang work.
--
You received this message because you are subscribed to the Google Groups
How is it possible to build the kernel with Clang with the
-fsanitize=safe-stack option?
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
I mostly followed this page and the GCC error was due to not having GCC-C++
installed. After that, all was well!
$ sudo yum install gcc-c++
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving
On Fri, March 30, 2018 3:35 pm, sevas wrote:
> Can someone please point me in the right direction? I don't know where to
> look.
>
> I've created a standalone Fedora 26 and I'm looking at this page, the
> qubes page : working with kernel,
>
> I've installed every Palast I can think of.
>
>
> Error
Can someone please point me in the right direction? I don't know where to look.
I've created a standalone Fedora 26 and I'm looking at this page, the qubes
page : working with kernel,
I've installed every Palast I can think of.
Error gcc plug-ins installation does not support plug-ins...
On Tuesday, November 28, 2017 at 6:41:02 PM UTC+1, Frédéric Pierret (fepitre)
wrote:
> Le mardi 28 novembre 2017 18:33:38 UTC+1, Foppe de Haan a écrit :
> > guest-wd.log from a (fedora) VM that won't boot with kernel-qubes-vm-4.14.2:
>
> I confirm your log and the behavior. Few days ago, I tried
fepitre, reg, FYI:
https://github.com/QubesOS/qubes-issues/issues/3404#issuecomment-355724725
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
Thanks, Reg. :)
On the topic of 4.14 in dom0: When I compile stuff in a VM (with 8 or 10 out of
12 threads assigned), I am sometimes running into cursor and other sluggishness
in dom0 and (the rendering of) other VMs, when this wasn't ever the case (to my
recollection) in kernels <=4.12. IIRC
On 11/25/2017 05:51 AM, Foppe de Haan wrote:
> On Friday, November 24, 2017 at 6:00:37 PM UTC+1, Foppe de Haan wrote:
>> On Friday, November 24, 2017 at 3:25:40 PM UTC+1, Frédéric Pierret (fepitre)
>> wrote:
>>> Le vendredi 24 novembre 2017 15:22:20 UTC+1, Foppe de Haan a écrit :
On
On Tuesday, November 28, 2017 at 6:41:02 PM UTC+1, Frédéric Pierret (fepitre)
wrote:
> Le mardi 28 novembre 2017 18:33:38 UTC+1, Foppe de Haan a écrit :
> > guest-wd.log from a (fedora) VM that won't boot with kernel-qubes-vm-4.14.2:
>
> I confirm your log and the behavior. Few days ago, I tried
On Tuesday, November 28, 2017 at 6:41:02 PM UTC+1, Frédéric Pierret (fepitre)
wrote:
> Le mardi 28 novembre 2017 18:33:38 UTC+1, Foppe de Haan a écrit :
> > guest-wd.log from a (fedora) VM that won't boot with kernel-qubes-vm-4.14.2:
>
> I confirm your log and the behavior. Few days ago, I tried
Le mardi 28 novembre 2017 18:33:38 UTC+1, Foppe de Haan a écrit :
> guest-wd.log from a (fedora) VM that won't boot with kernel-qubes-vm-4.14.2:
I confirm your log and the behavior. Few days ago, I tried to look on the xen
and kernel list to see if there were something bug we need to dig into
guest-wd.log from a (fedora) VM that won't boot with kernel-qubes-vm-4.14.2:
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
On Friday, November 24, 2017 at 6:00:37 PM UTC+1, Foppe de Haan wrote:
> On Friday, November 24, 2017 at 3:25:40 PM UTC+1, Frédéric Pierret (fepitre)
> wrote:
> > Le vendredi 24 novembre 2017 15:22:20 UTC+1, Foppe de Haan a écrit :
> > > On Thursday, November 23, 2017 at 9:30:30 PM UTC+1,
On Friday, November 24, 2017 at 7:01:37 PM UTC+1, Frédéric Pierret (fepitre)
wrote:
> Le vendredi 24 novembre 2017 18:00:37 UTC+1, Foppe de Haan a écrit :
> > On Friday, November 24, 2017 at 3:25:40 PM UTC+1, Frédéric Pierret
> > (fepitre) wrote:
> > > Le vendredi 24 novembre 2017 15:22:20
Le vendredi 24 novembre 2017 18:00:37 UTC+1, Foppe de Haan a écrit :
> On Friday, November 24, 2017 at 3:25:40 PM UTC+1, Frédéric Pierret (fepitre)
> wrote:
> > Le vendredi 24 novembre 2017 15:22:20 UTC+1, Foppe de Haan a écrit :
> > > On Thursday, November 23, 2017 at 9:30:30 PM UTC+1, Frédéric
On Friday, November 24, 2017 at 3:25:40 PM UTC+1, Frédéric Pierret (fepitre)
wrote:
> Le vendredi 24 novembre 2017 15:22:20 UTC+1, Foppe de Haan a écrit :
> > On Thursday, November 23, 2017 at 9:30:30 PM UTC+1, Frédéric Pierret
> > (fepitre) wrote:
> > > Le mercredi 22 novembre 2017 18:31:29
Le vendredi 24 novembre 2017 15:22:20 UTC+1, Foppe de Haan a écrit :
> On Thursday, November 23, 2017 at 9:30:30 PM UTC+1, Frédéric Pierret
> (fepitre) wrote:
> > Le mercredi 22 novembre 2017 18:31:29 UTC+1, Foppe de Haan a écrit :
> > > Now that 4.14's reached stable, does anyone plan to test it
On Thursday, November 23, 2017 at 9:30:30 PM UTC+1, Frédéric Pierret (fepitre)
wrote:
> Le mercredi 22 novembre 2017 18:31:29 UTC+1, Foppe de Haan a écrit :
> > Now that 4.14's reached stable, does anyone plan to test it soon (or have
> > an idea when they'll have time to do so)? Since 4.13
Le mercredi 22 novembre 2017 18:31:29 UTC+1, Foppe de Haan a écrit :
> Now that 4.14's reached stable, does anyone plan to test it soon (or have an
> idea when they'll have time to do so)? Since 4.13 wasn't stable 'by default'
> in qubes, I would assume 4.14 won't be either, but although I'll
Le mercredi 22 novembre 2017 18:31:29 UTC+1, Foppe de Haan a écrit :
> Now that 4.14's reached stable, does anyone plan to test it soon (or have an
> idea when they'll have time to do so)? Since 4.13 wasn't stable 'by default'
> in qubes, I would assume 4.14 won't be either, but although I'll
Now that 4.14's reached stable, does anyone plan to test it soon (or have an
idea when they'll have time to do so)? Since 4.13 wasn't stable 'by default' in
qubes, I would assume 4.14 won't be either, but although I'll certainly give it
a go, I'm fairly sure I am not the best person to try to
On Sunday, October 15, 2017 at 10:11:16 AM UTC+2, Foppe de Haan wrote:
> I've just tried 4.13 again, still getting the same behavior, with the mouse
> cursor becoming progressively less responsive, and mouse and kb both becoming
> unresponsive, then X crashing/dying some time after that. Looking
I've just tried 4.13 again, still getting the same behavior, with the mouse
cursor becoming progressively less responsive, and mouse and kb both becoming
unresponsive, then X crashing/dying some time after that. Looking at the
(kernel) logs for that boot, I don't really see anything obvious by
On Monday, October 2, 2017 at 11:35:37 AM UTC+2, Frédéric Pierret (fepitre)
wrote:
> Le lundi 2 octobre 2017 02:36:48 UTC+2, Reg Tiangha a écrit :
> > On 2017-10-01 10:21 AM, Frédéric Pierret (fepitre) wrote:
> >
> > >
> > > Hi, just a small update of current kernel branches status:
> > >
> >
Le lundi 2 octobre 2017 02:36:48 UTC+2, Reg Tiangha a écrit :
> On 2017-10-01 10:21 AM, Frédéric Pierret (fepitre) wrote:
>
> >
> > Hi, just a small update of current kernel branches status:
> >
> > From our last commits with Reg, the last version of kernel 4.12.14 is
> > available and also I
On 2017-10-01 10:21 AM, Frédéric Pierret (fepitre) wrote:
>
> Hi, just a small update of current kernel branches status:
>
> From our last commits with Reg, the last version of kernel 4.12.14 is
> available and also I created the branch for devel-4.13 (currently version
> 4.13.4).
>
> From
Le vendredi 14 avril 2017 20:21:29 UTC+2, Reg Tiangha a écrit :
> Here's my contribution to the project.
>
> On my GitHub account, I've now got branches tracking kernels from 4.4
> all the way to 4.10. My intent is to keep them up-to-date with upstream
> as much as possible, but all I can really
W dniu niedziela, 13 sierpnia 2017 07:24:29 UTC+2 użytkownik Foppe de Haan
napisał:
> For any newcomers: can you tell me if this covers all the bases?
> https://github.com/0spinboson/qubes-doc/blob/patch-1/managing-os/compiling-your-own-kernel.md
> (or if not, what's missing?)
It needs to
W dniu niedziela, 13 sierpnia 2017 14:17:33 UTC+2 użytkownik Epitre napisał:
> Le dimanche 13 août 2017 09:41:53 UTC+2, Foppe de Haan a écrit :
> > On Sunday, August 13, 2017 at 9:38:06 AM UTC+2, Epitre wrote:
> > > Le dimanche 13 août 2017 09:19:25 UTC+2, Epitre a écrit :
> > > > Le dimanche 13
make also has an option of automatically detecting all loaded modules (via
lsmod) and compiling the kernel only with support for currently loaded modules.
Use make localmodconfig for that.
Running it in a vm wouldn't be such a good idea since the module config for
dom0 and appvms differ greatly
Le lundi 14 août 2017 00:29:41 UTC+2, Yethal a écrit :
> W dniu niedziela, 13 sierpnia 2017 22:45:01 UTC+2 użytkownik Grzesiek
> Chodzicki napisał:
> > W dniu niedziela, 13 sierpnia 2017 14:17:33 UTC+2 użytkownik Epitre napisał:
> > > Le dimanche 13 août 2017 09:41:53 UTC+2, Foppe de Haan a écrit
W dniu niedziela, 13 sierpnia 2017 14:17:33 UTC+2 użytkownik Epitre napisał:
> Le dimanche 13 août 2017 09:41:53 UTC+2, Foppe de Haan a écrit :
> > On Sunday, August 13, 2017 at 9:38:06 AM UTC+2, Epitre wrote:
> > > Le dimanche 13 août 2017 09:19:25 UTC+2, Epitre a écrit :
> > > > Le dimanche 13
Le dimanche 13 août 2017 09:41:53 UTC+2, Foppe de Haan a écrit :
> On Sunday, August 13, 2017 at 9:38:06 AM UTC+2, Epitre wrote:
> > Le dimanche 13 août 2017 09:19:25 UTC+2, Epitre a écrit :
> > > Le dimanche 13 août 2017 07:24:29 UTC+2, Foppe de Haan a écrit :
> > > > For any newcomers: can you
Le dimanche 13 août 2017 09:19:25 UTC+2, Epitre a écrit :
> Le dimanche 13 août 2017 07:24:29 UTC+2, Foppe de Haan a écrit :
> > For any newcomers: can you tell me if this covers all the bases?
> > https://github.com/0spinboson/qubes-doc/blob/patch-1/managing-os/compiling-your-own-kernel.md
> >
Le dimanche 13 août 2017 07:24:29 UTC+2, Foppe de Haan a écrit :
> For any newcomers: can you tell me if this covers all the bases?
> https://github.com/0spinboson/qubes-doc/blob/patch-1/managing-os/compiling-your-own-kernel.md
> (or if not, what's missing?)
Hi,
It seems right for me. Just a a
For any newcomers: can you tell me if this covers all the bases?
https://github.com/0spinboson/qubes-doc/blob/patch-1/managing-os/compiling-your-own-kernel.md
(or if not, what's missing?)
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To
On Sunday, August 13, 2017 at 12:02:09 AM UTC+2, Grzesiek Chodzicki wrote:
> W dniu sobota, 12 sierpnia 2017 19:41:36 UTC+2 użytkownik Foppe de Haan
> napisał:
> > On Saturday, August 12, 2017 at 7:27:45 PM UTC+2, Grzesiek Chodzicki wrote:
> > > W dniu sobota, 12 sierpnia 2017 18:48:44 UTC+2
W dniu sobota, 12 sierpnia 2017 19:41:36 UTC+2 użytkownik Foppe de Haan napisał:
> On Saturday, August 12, 2017 at 7:27:45 PM UTC+2, Grzesiek Chodzicki wrote:
> > W dniu sobota, 12 sierpnia 2017 18:48:44 UTC+2 użytkownik Foppe de Haan
> > napisał:
> > > On Saturday, August 12, 2017 at 6:41:33 PM
On Saturday, August 12, 2017 at 7:27:45 PM UTC+2, Grzesiek Chodzicki wrote:
> W dniu sobota, 12 sierpnia 2017 18:48:44 UTC+2 użytkownik Foppe de Haan
> napisał:
> > On Saturday, August 12, 2017 at 6:41:33 PM UTC+2, Grzesiek Chodzicki wrote:
> > > On my machine the compilation fails with a non
W dniu sobota, 12 sierpnia 2017 18:48:44 UTC+2 użytkownik Foppe de Haan napisał:
> On Saturday, August 12, 2017 at 6:41:33 PM UTC+2, Grzesiek Chodzicki wrote:
> > On my machine the compilation fails with a non obvious error
> > Makefile:90: recipe for target 'rpms-dom0' failed
> > make: ***
On Saturday, August 12, 2017 at 6:41:33 PM UTC+2, Grzesiek Chodzicki wrote:
> On my machine the compilation fails with a non obvious error
> Makefile:90: recipe for target 'rpms-dom0' failed
> make: *** [rpms-dom0] Error 1
>
> This is in a f25 based machine. Would it be possible to have the
On my machine the compilation fails with a non obvious error
Makefile:90: recipe for target 'rpms-dom0' failed
make: *** [rpms-dom0] Error 1
This is in a f25 based machine. Would it be possible to have the entire thing
in chroot or a docker container?
--
You received this message because you
Wrt (4.11) build dependencies: you'll also need elfutils-libelf-devel,
gcc-plugin-devel.
as before, it's easiest to build these in a fc23-based VM.
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop
On 06/27/2017 04:50 PM,
0spinbo...@gmail.com wrote:
> It seems building works fine on fc23. Wonder what changed between 6/17 and
> today that fc25 no longer compiles kernels, though.
>
> Wasn't using any patches from the hardening project.
I just spun up a FC25 BuildVM and *no* kernels (I even
On Tuesday, June 27, 2017 at 10:42:51 PM UTC+2, Reg Tiangha wrote:
> On 2017-06-27 1:53 PM, Reg Tiangha wrote:
> > On 2017-06-27 1:37 PM,
> > 0spinboson wrote:
> >
> >> Thanks. Was already up to date, though, and all gzip-related options were
> >> enabled (as before). Only change was a new
On 2017-06-27 1:53 PM, Reg Tiangha wrote:
> On 2017-06-27 1:37 PM,
> 0spinbo...@gmail.com wrote:
>
>> Thanks. Was already up to date, though, and all gzip-related options were
>> enabled (as before). Only change was a new package req
>> (elfutils-libelf-devel).
>> As for new info, I have
On Tuesday, June 27, 2017 at 8:28:55 PM UTC+2, Reg Tiangha wrote:
> On 06/27/2017 08:09 AM, Epitre wrote:
> > Le mardi 27 juin 2017 12:40:00 UTC+2, 0spin...@gmail.com a écrit :
> >> Anyone have an idea why, since 4.11.7, I am always getting a "initramfs
> >> not in gzip format" error?
> > Hi,
On 06/27/2017 08:09 AM, Epitre wrote:
> Le mardi 27 juin 2017 12:40:00 UTC+2, 0spin...@gmail.com a écrit :
>> Anyone have an idea why, since 4.11.7, I am always getting a "initramfs not
>> in gzip format" error?
> Hi, same problem for me with 4.11.7. I also tried to select only AMD family
> (my
Le mardi 27 juin 2017 12:40:00 UTC+2, 0spin...@gmail.com a écrit :
> Anyone have an idea why, since 4.11.7, I am always getting a "initramfs not
> in gzip format" error?
Hi, same problem for me with 4.11.7. I also tried to select only AMD family (my
type of processor) and it results the same.
Anyone have an idea why, since 4.11.7, I am always getting a "initramfs not in
gzip format" error?
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
OK, thanks. It seems I have compiled it with slightly newer set of patches
(4.8.14-12 vs. 4.8.14-9). I haven't noticed the unstable repo
(https://yum.qubes-os.org/r3.2/unstable/dom0/fc23/rpm/ )…
I don't see it in official repo. Is it compiled from slightly older version of
On 04/28/2017 11:56 PM, Foppe de Haan wrote:
> the update wasn't built for the fc23-vm:
> https://github.com/QubesOS/updates-status/issues/17
>
That's really weird, since it came out for dom0, which is essentially
fc23. And it looks like the fc24 and 25 versions never transferred over
from
On Saturday, April 29, 2017 at 1:56:42 AM UTC-4, Foppe de Haan wrote:
> the update wasn't built for the fc23-vm:
> https://github.com/QubesOS/updates-status/issues/17
Thanks.
somehow I never found that page during google searching.
--
You received this message because you are subscribed to
the update wasn't built for the fc23-vm:
https://github.com/QubesOS/updates-status/issues/17
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
On 04/28/2017 11:20 PM, gho...@gmail.com
wrote:
>> I don't know why it wouldn't work for you, unless you're running a
>> version of Qubes older than R3.2 or using an unsupported Fedora template.
>>
>> As a last resort, you can replace your /usr/src/u2mfn-3.2.3/u2mfn.c file
>> with this one here:
> I don't know why it wouldn't work for you, unless you're running a
> version of Qubes older than R3.2 or using an unsupported Fedora template.
>
> As a last resort, you can replace your /usr/src/u2mfn-3.2.3/u2mfn.c file
> with this one here:
>
>
On 04/28/2017 10:25 PM, gho...@gmail.com
wrote:
>> You need to update the qubes-kernel-vm-support package in the Fedora VM
>> that you're trying to compile this in. A compatible version (3.2.4)
>> should has been pushed out to the stable repositories so running sudo
>> dnf upgrade should pull it
> >
> You need to update the qubes-kernel-vm-support package in the Fedora VM
> that you're trying to compile this in. A compatible version (3.2.4)
> should has been pushed out to the stable repositories so running sudo
> dnf upgrade should pull it in (unless you've never installed it in the
>
On 04/28/2017 09:03 PM, gho...@gmail.com
wrote:
> Hello,
>
> I am following your instructions and trying to compile devel-4.10. I am
> getting the following error. This error also occurs on stable-4.9. Any idea
> how i can fix this.
>
> Thanks.
>
> /home/user/qubes-linux-kernel/u2mfn/u2mfn.c:
Hello,
I am following your instructions and trying to compile devel-4.10. I am
getting the following error. This error also occurs on stable-4.9. Any idea
how i can fix this.
Thanks.
/home/user/qubes-linux-kernel/u2mfn/u2mfn.c: In function 'u2mfn_ioctl':
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2017-04-16 18:21, Reg Tiangha wrote:
>> On 2017-04-16 18:10, Marek Marczykowski-Górecki wrote:
>>> On Fri, Apr 14, 2017 at 12:21:14PM -0600, Reg Tiangha wrote:
Here's my contribution to the project.
>>> Thanks!
>>>
>>> Andrew, maybe it
On 04/16/2017 07:16 PM, Andrew David Wong wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> On 2017-04-16 18:10, Marek Marczykowski-Górecki wrote:
>> On Fri, Apr 14, 2017 at 12:21:14PM -0600, Reg Tiangha wrote:
>>> Here's my contribution to the project.
>> Thanks!
>>
>> Andrew, maybe
On 04/15/2017 04:44 AM, Foppe de Haan wrote:
> also needed: rpm-sign, sparse, openssl-devel
>
> and creating a signing key, see e.g. here: http://fedoranews.org/tchung/gpg/
>
Thanks for all of that.
The signing part isn't that important though, unless you were planning
on distributing the
make menuconfig also requires ncurses-devel
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send
On 04/14/2017 02:29 PM, Reg Tiangha wrote:
> On 04/14/2017 02:22 PM, Foppe de Haan wrote:
>> 1. Thanks. :)
>> 2. Starting from a vanilla f23-template, I also had to install rpm-build
>> (non-obvious 'error 8').
>>
> Thanks. And I just remembered that you'll probably need to install the
> latest
On 04/14/2017 02:22 PM, Foppe de Haan wrote:
> 1. Thanks. :)
> 2. Starting from a vanilla f23-template, I also had to install rpm-build
> (non-obvious 'error 8').
>
Thanks. And I just remembered that you'll probably need to install the
latest version of qubes-utils in dom0 too if you want to run
1. Thanks. :)
2. Starting from a vanilla f23-template, I also had to install rpm-build
(non-obvious 'error 8').
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
On 04/14/2017 12:21 PM, Reg Tiangha wrote:
> Here's my contribution to the project.
>
> On my GitHub account, I've now got branches tracking kernels from 4.4
> all the way to 4.10. My intent is to keep them up-to-date with upstream
> as much as possible, but all I can really test is to see is if
69 matches
Mail list logo
