You can subscribe to this list here.
1999 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(8) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2000 |
Jan
(19) |
Feb
(11) |
Mar
(56) |
Apr
(31) |
May
(37) |
Jun
(21) |
Jul
(30) |
Aug
(31) |
Sep
(25) |
Oct
(60) |
Nov
(28) |
Dec
(57) |
2001 |
Jan
(47) |
Feb
(119) |
Mar
(279) |
Apr
(198) |
May
(336) |
Jun
(201) |
Jul
(136) |
Aug
(123) |
Sep
(123) |
Oct
(185) |
Nov
(66) |
Dec
(97) |
2002 |
Jan
(318) |
Feb
(101) |
Mar
(167) |
Apr
(233) |
May
(249) |
Jun
(134) |
Jul
(195) |
Aug
(99) |
Sep
(278) |
Oct
(435) |
Nov
(326) |
Dec
(325) |
2003 |
Jan
(214) |
Feb
(309) |
Mar
(142) |
Apr
(141) |
May
(210) |
Jun
(86) |
Jul
(133) |
Aug
(218) |
Sep
(315) |
Oct
(152) |
Nov
(162) |
Dec
(288) |
2004 |
Jan
(277) |
Feb
(267) |
Mar
(182) |
Apr
(168) |
May
(254) |
Jun
(131) |
Jul
(168) |
Aug
(177) |
Sep
(262) |
Oct
(309) |
Nov
(262) |
Dec
(255) |
2005 |
Jan
(258) |
Feb
(169) |
Mar
(282) |
Apr
(208) |
May
(262) |
Jun
(187) |
Jul
(207) |
Aug
(171) |
Sep
(283) |
Oct
(216) |
Nov
(307) |
Dec
(107) |
2006 |
Jan
(207) |
Feb
(82) |
Mar
(192) |
Apr
(165) |
May
(121) |
Jun
(108) |
Jul
(120) |
Aug
(126) |
Sep
(101) |
Oct
(216) |
Nov
(95) |
Dec
(125) |
2007 |
Jan
(176) |
Feb
(117) |
Mar
(240) |
Apr
(120) |
May
(81) |
Jun
(82) |
Jul
(62) |
Aug
(120) |
Sep
(103) |
Oct
(109) |
Nov
(181) |
Dec
(87) |
2008 |
Jan
(145) |
Feb
(69) |
Mar
(31) |
Apr
(98) |
May
(91) |
Jun
(43) |
Jul
(68) |
Aug
(135) |
Sep
(48) |
Oct
(18) |
Nov
(29) |
Dec
(16) |
2009 |
Jan
(26) |
Feb
(15) |
Mar
(83) |
Apr
(39) |
May
(23) |
Jun
(35) |
Jul
(11) |
Aug
(3) |
Sep
(11) |
Oct
(2) |
Nov
(28) |
Dec
(8) |
2010 |
Jan
(4) |
Feb
(40) |
Mar
(4) |
Apr
(46) |
May
(35) |
Jun
(46) |
Jul
(10) |
Aug
(4) |
Sep
(50) |
Oct
(70) |
Nov
(31) |
Dec
(24) |
2011 |
Jan
(17) |
Feb
(8) |
Mar
(35) |
Apr
(50) |
May
(75) |
Jun
(55) |
Jul
(72) |
Aug
(272) |
Sep
(10) |
Oct
(9) |
Nov
(11) |
Dec
(15) |
2012 |
Jan
(36) |
Feb
(49) |
Mar
(54) |
Apr
(47) |
May
(8) |
Jun
(82) |
Jul
(20) |
Aug
(50) |
Sep
(51) |
Oct
(20) |
Nov
(10) |
Dec
(25) |
2013 |
Jan
(34) |
Feb
(4) |
Mar
(24) |
Apr
(40) |
May
(101) |
Jun
(30) |
Jul
(55) |
Aug
(84) |
Sep
(53) |
Oct
(49) |
Nov
(61) |
Dec
(36) |
2014 |
Jan
(26) |
Feb
(22) |
Mar
(30) |
Apr
(4) |
May
(43) |
Jun
(33) |
Jul
(44) |
Aug
(61) |
Sep
(46) |
Oct
(154) |
Nov
(16) |
Dec
(12) |
2015 |
Jan
(18) |
Feb
(2) |
Mar
(122) |
Apr
(23) |
May
(56) |
Jun
(29) |
Jul
(35) |
Aug
(15) |
Sep
|
Oct
(45) |
Nov
(94) |
Dec
(38) |
2016 |
Jan
(50) |
Feb
(39) |
Mar
(39) |
Apr
(1) |
May
(14) |
Jun
(12) |
Jul
(19) |
Aug
(12) |
Sep
(9) |
Oct
(1) |
Nov
(13) |
Dec
(7) |
2017 |
Jan
(6) |
Feb
(1) |
Mar
(16) |
Apr
(5) |
May
(61) |
Jun
(18) |
Jul
(43) |
Aug
(1) |
Sep
(8) |
Oct
(25) |
Nov
(30) |
Dec
(6) |
2018 |
Jan
(5) |
Feb
(2) |
Mar
(25) |
Apr
(15) |
May
(2) |
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
2019 |
Jan
|
Feb
(2) |
Mar
|
Apr
(1) |
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Richard W. <ri...@no...> - 2018-03-29 20:34:55
|
Am Donnerstag, 29. März 2018, 22:20:47 CEST schrieb Joel Fernandes: > Thanks a lot! I am wondering why the same compiler works when running > the test for a regular image. Maybe different compiler flags. Anyway > good to learn this. > > Also one more slightly OT question, why is UML only doing UP ? Is it > extremely hard to do SMP for UML? Long story short, nobody implemented SMP so far. :-) Because SKAS3/0 we had a SMP implementation of TT mode. In terms of UML implementing SMP means having multiple threads that handle the userspace loop in arch/um/os-Linux/skas/process.c. We could also do a poor man's SMP implementation first, where only user processes run in parallel. IOW userspace() in arch/um/os-Linux/skas/process.c is still a single thread but it let's run up to N user space thread and only if the call into the kernel we degrade to UP. Adding SMP is not extremely hard but it requires a lot of re-work of the UML core and introduces tons of new issues. That said, volunteers are welcome! Thanks, //richard |
From: Joel F. <agn...@gm...> - 2018-03-29 20:20:56
|
On Wed, Mar 28, 2018 at 11:04 PM, Geert Uytterhoeven <ge...@li...> wrote: > On Thu, Mar 29, 2018 at 12:35 AM, Richard Weinberger <ri...@no...> wrote: >> Am Donnerstag, 29. März 2018, 00:19:39 CEST schrieb Joel Fernandes: >>> On Wed, Mar 28, 2018 at 6:19 AM, Richard Weinberger <ri...@no...> wrote: >>> > Am Mittwoch, 28. März 2018, 15:11:29 CEST schrieb Geert Uytterhoeven: >>> >> On Wed, Mar 28, 2018 at 12:28 PM, Joel Fernandes <agn...@gm...> >>> > wrote: >>> >> > while(release_now == 0); >>> >> >>> >> while (release_now == 0) >>> >> cpu_relax(); >>> > >>> > Not sure whether a cpu_relax() fixes the problem. >>> > I guess the root of the problem is that UML is UP and non-preemptive. >>> > Therefore the loop is never interrupted. >>> > To verify I asked for the full source. >>> > >>> >>> cpu_relax actually worked! >> >> Interesting. >> >>> Any thoughts on why it helps? Even if its non-preemptive, I did >>> receive the timer interrupt, so I expected the variable to be set. >> >> Timers trigger also with preempt off, I forgot... >> I think the cpu_relax() issues internally a barrier such that the >> release_now variable is read again. >> Can you try barrier() instead of cpu_relax()? I bet it works too. >> Same if you mark release_now as volatile. > > Without cpu_relax()/barrier()/volatile, the compiler can assume release_now > never changes, and thus may "optimize" the loop to an infinite loop. > Thanks a lot! I am wondering why the same compiler works when running the test for a regular image. Maybe different compiler flags. Anyway good to learn this. Also one more slightly OT question, why is UML only doing UP ? Is it extremely hard to do SMP for UML? I also happen to notice Qemu has one thread per emulated core... thanks, - Joel |
From: Richard W. <ri...@no...> - 2018-03-29 20:18:41
|
Am Montag, 5. März 2018, 14:29:05 CEST schrieb ant...@ca...: > From: Anton Ivanov <ant...@ca...> > > Vector RAW in UML needs to BPF filter its own MAC only > if QDISC_BYPASS has failed. If QDISC_BYPASS is successful, the > frames originated locally are not visible to readers on the > raw socket. > > Signed-off-by: Anton Ivanov <ant...@ca...> Applied. Thanks, //richard |
From: Richard W. <ri...@no...> - 2018-03-29 20:17:40
|
Am Montag, 5. März 2018, 11:41:42 CEST schrieb ant...@ca...: > From: Anton Ivanov <ant...@ca...> > > The patches for the UML vector drivers were in-flight when > the timer changes happened and were not covered by them. > > This change migrates vector_kern.c to use the new timer API. > > Signed-off-by: Anton Ivanov <ant...@ca...> Applied. Thanks, //richard |
From: Geert U. <ge...@li...> - 2018-03-29 06:04:30
|
On Thu, Mar 29, 2018 at 12:35 AM, Richard Weinberger <ri...@no...> wrote: > Am Donnerstag, 29. März 2018, 00:19:39 CEST schrieb Joel Fernandes: >> On Wed, Mar 28, 2018 at 6:19 AM, Richard Weinberger <ri...@no...> wrote: >> > Am Mittwoch, 28. März 2018, 15:11:29 CEST schrieb Geert Uytterhoeven: >> >> On Wed, Mar 28, 2018 at 12:28 PM, Joel Fernandes <agn...@gm...> >> > wrote: >> >> > while(release_now == 0); >> >> >> >> while (release_now == 0) >> >> cpu_relax(); >> > >> > Not sure whether a cpu_relax() fixes the problem. >> > I guess the root of the problem is that UML is UP and non-preemptive. >> > Therefore the loop is never interrupted. >> > To verify I asked for the full source. >> > >> >> cpu_relax actually worked! > > Interesting. > >> Any thoughts on why it helps? Even if its non-preemptive, I did >> receive the timer interrupt, so I expected the variable to be set. > > Timers trigger also with preempt off, I forgot... > I think the cpu_relax() issues internally a barrier such that the > release_now variable is read again. > Can you try barrier() instead of cpu_relax()? I bet it works too. > Same if you mark release_now as volatile. Without cpu_relax()/barrier()/volatile, the compiler can assume release_now never changes, and thus may "optimize" the loop to an infinite loop. Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@li... In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds |
From: Richard W. <ri...@no...> - 2018-03-28 22:35:23
|
Am Donnerstag, 29. März 2018, 00:19:39 CEST schrieb Joel Fernandes: > Thanks for the quick reply. > > On Wed, Mar 28, 2018 at 6:19 AM, Richard Weinberger <ri...@no...> wrote: > > Am Mittwoch, 28. März 2018, 15:11:29 CEST schrieb Geert Uytterhoeven: > >> On Wed, Mar 28, 2018 at 12:28 PM, Joel Fernandes <agn...@gm...> > > wrote: > >> > while(release_now == 0); > >> > >> while (release_now == 0) > >> cpu_relax(); > > > > Not sure whether a cpu_relax() fixes the problem. > > I guess the root of the problem is that UML is UP and non-preemptive. > > Therefore the loop is never interrupted. > > To verify I asked for the full source. > > > > cpu_relax actually worked! Interesting. > Any thoughts on why it helps? Even if its non-preemptive, I did > receive the timer interrupt, so I expected the variable to be set. Timers trigger also with preempt off, I forgot... I think the cpu_relax() issues internally a barrier such that the release_now variable is read again. Can you try barrier() instead of cpu_relax()? I bet it works too. Same if you mark release_now as volatile. Thanks, //richard |
From: Joel F. <agn...@gm...> - 2018-03-28 22:19:49
|
Thanks for the quick reply. On Wed, Mar 28, 2018 at 6:19 AM, Richard Weinberger <ri...@no...> wrote: > Am Mittwoch, 28. März 2018, 15:11:29 CEST schrieb Geert Uytterhoeven: >> On Wed, Mar 28, 2018 at 12:28 PM, Joel Fernandes <agn...@gm...> > wrote: >> > while(release_now == 0); >> >> while (release_now == 0) >> cpu_relax(); > > Not sure whether a cpu_relax() fixes the problem. > I guess the root of the problem is that UML is UP and non-preemptive. > Therefore the loop is never interrupted. > To verify I asked for the full source. > cpu_relax actually worked! Any thoughts on why it helps? Even if its non-preemptive, I did receive the timer interrupt, so I expected the variable to be set. Module is attached. Thanks, -Joel |
From: Richard W. <ri...@no...> - 2018-03-28 13:19:22
|
Am Mittwoch, 28. März 2018, 15:11:29 CEST schrieb Geert Uytterhoeven: > On Wed, Mar 28, 2018 at 12:28 PM, Joel Fernandes <agn...@gm...> wrote: > > while(release_now == 0); > > while (release_now == 0) > cpu_relax(); Not sure whether a cpu_relax() fixes the problem. I guess the root of the problem is that UML is UP and non-preemptive. Therefore the loop is never interrupted. To verify I asked for the full source. Thanks, //richard |
From: Geert U. <ge...@li...> - 2018-03-28 13:11:39
|
On Wed, Mar 28, 2018 at 12:28 PM, Joel Fernandes <agn...@gm...> wrote: > while(release_now == 0); while (release_now == 0) cpu_relax(); Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@li... In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds |
From: Richard W. <ri...@no...> - 2018-03-28 11:22:45
|
Am Mittwoch, 28. März 2018, 12:28:02 CEST schrieb Joel Fernandes: > Hi, > > I wrote a kernel module to play with hrtimer subsystem and it hangs > with UML, Any ideas on why it may be hanging? It doesn't hang on any > of my other machines. Hopefully I'm not doing something stupid, but I > don't think I am.. > > It appears the timer handler does fire. However, the UML process is > continously doing a kill(SIGALRM) to the host, and the shell hangs. > Here's the continous strace output of UML's process at the time of the > hang: https://hastebin.com/ikehadapon.sql > > To build UML, I do: > make ARCH=um x86_64_defconfig > > UML kernel version is v4.16-rc4 > > Here's the module I'm loading: Please share the full sources that compile. The I can have a look. Thanks, //richard |
From: Joel F. <agn...@gm...> - 2018-03-28 10:28:11
|
Hi, I wrote a kernel module to play with hrtimer subsystem and it hangs with UML, Any ideas on why it may be hanging? It doesn't hang on any of my other machines. Hopefully I'm not doing something stupid, but I don't think I am.. It appears the timer handler does fire. However, the UML process is continously doing a kill(SIGALRM) to the host, and the shell hangs. Here's the continous strace output of UML's process at the time of the hang: https://hastebin.com/ikehadapon.sql To build UML, I do: make ARCH=um x86_64_defconfig UML kernel version is v4.16-rc4 Here's the module I'm loading: static enum hrtimer_restart bigtimer_handle(struct hrtimer *timer) { printk(KERN_ERR "timer fired 2\n"); spin_lock(&il->biglock); spin_unlock(&il->biglock); release_now = 1; return HRTIMER_NORESTART; } void init_bigstr(struct bigstr *b) { spin_lock_init(&b->biglock); } static int __init test_module_init(void) { struct bigstr b1, b2; struct hrtimer *timer; release_now = 0; init_bigstr(&b1); init_bigstr(&b2); timer = &bigtimer; timer->debug = 1; hrtimer_init(timer, CLOCK_MONOTONIC, HRTIMER_MODE_REL); timer->function = bigtimer_handle; il = &b2; spin_lock(&b1.biglock); printk(KERN_ERR "Starting timer\n"); hrtimer_start(timer, ns_to_ktime(50000ULL), HRTIMER_MODE_REL_PINNED); while(release_now == 0); spin_unlock(&b1.biglock); return -1; } Thanks for any debug thoughts! I'll also try to hook up gdb tomorrow and see if I find something.. Regards, - Joel |
From: Richard W. <ri...@no...> - 2018-03-20 14:51:57
|
Am Dienstag, 20. März 2018, 03:45:11 CET schrieb Bernd Petrovitsch: > On Mon, 2018-03-19 at 15:24 +0100, Richard Weinberger wrote: > [...] > > > I checked, migrating is not an option. > > sourceforge has hacked mailman to hide member mail addresses: > > "As a result of the latest electronic messaging and privacy requirements > > around the world, SourceForge has implemented a number of changes that > > affect > Details please, sf.net. > Otherwise the motivation is very probably a completely different one. > > > email privacy. One part of this is that it is no longer possible for > > project admins to view the member emails of their mailing lists." > > As absurd as it can get if an ML admin isn't allowed to see the email > addresses on his/her list. > > It seems sf.net wants to be abandoned in general .... > > Just create the new - better - list/s and send subscription > information! I've talked to dwmw2, we will move to infradead.org. :-) Thanks, //richard |
From: Bernd P. <be...@pe...> - 2018-03-20 02:46:01
|
On Mon, 2018-03-19 at 15:24 +0100, Richard Weinberger wrote: [...] > I checked, migrating is not an option. > sourceforge has hacked mailman to hide member mail addresses: > "As a result of the latest electronic messaging and privacy requirements > around the world, SourceForge has implemented a number of changes that affect Details please, sf.net. Otherwise the motivation is very probably a completely different one. > email privacy. One part of this is that it is no longer possible for project > admins to view the member emails of their mailing lists." As absurd as it can get if an ML admin isn't allowed to see the email addresses on his/her list. It seems sf.net wants to be abandoned in general .... Just create the new - better - list/s and send subscription information! MfG, Bernd -- Bernd Petrovitsch Email : be...@pe... LUGA : http://www.luga.at |
From: Richard W. <ri...@no...> - 2018-03-19 14:23:10
|
Am Dienstag, 13. März 2018, 14:59:41 CET schrieb Richard Weinberger: > Am Dienstag, 13. März 2018, 14:24:23 CET schrieb Geert Uytterhoeven: > > Hi Richard, > > > > On Mon, Mar 12, 2018 at 4:21 PM, Richard Weinberger <ri...@no...> wrote: > > > Am Montag, 12. März 2018, 16:10:45 CET schrieb Brandeburg, Jesse: > > >> > Is the list working for everyone? > > >> > > >> I got this mail... BTW Sourceforge had a major datacenter issue over > > >> the > > >> last few weeks, not sure if that broke something along the way. > > > > > > Hmm, I got this mail only because you CC'ed me. I don't see it in my > > > mailinglist inbox. > > > > > > We should bite the bullet and migrate way from sf.net, finally. > > > Any volunteers? > > > > You can ask DaveM to create a list at vger. > > Yes, or infradead.org. > The bigger problem is migrating all users. > > Maybe there is a way to extract a list of subscribers from > lists.sourceforge.net. Jeff made me project admin some time ago, maybe I can > exhume that account. I checked, migrating is not an option. sourceforge has hacked mailman to hide member mail addresses: "As a result of the latest electronic messaging and privacy requirements around the world, SourceForge has implemented a number of changes that affect email privacy. One part of this is that it is no longer possible for project admins to view the member emails of their mailing lists." > Or we are rude and expect everyone to re-subscribe to the new UML list. > That way we might lose 99% of all subscribers but at least the 1% is > interested in UML for sure. ;-) So, I'll ask for a mailinglist on infradead.org. Thanks, //richard P.s: Just realized that most of my mails also didn't make it to the mailinglist. That _sucks_. |
From: Anton I. <ant...@ko...> - 2018-03-13 14:05:15
|
On 03/13/18 13:59, Richard Weinberger wrote: > Am Dienstag, 13. März 2018, 14:24:23 CET schrieb Geert Uytterhoeven: >> Hi Richard, >> >> On Mon, Mar 12, 2018 at 4:21 PM, Richard Weinberger <ri...@no...> wrote: >>> Am Montag, 12. März 2018, 16:10:45 CET schrieb Brandeburg, Jesse: >>>>> Is the list working for everyone? >>>> I got this mail... BTW Sourceforge had a major datacenter issue over the >>>> last few weeks, not sure if that broke something along the way. >>> Hmm, I got this mail only because you CC'ed me. I don't see it in my >>> mailinglist inbox. >>> >>> We should bite the bullet and migrate way from sf.net, finally. >>> Any volunteers? >> You can ask DaveM to create a list at vger. > Yes, or infradead.org. > The bigger problem is migrating all users. > > Maybe there is a way to extract a list of subscribers from > lists.sourceforge.net. Jeff made me project admin some time ago, maybe I can > exhume that account. > > Or we are rude and expect everyone to re-subscribe to the new UML list. > That way we might lose 99% of all subscribers but at least the 1% is > interested in UML for sure. ;-) +1 > > Thanks, > //richard > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > User-mode-linux-devel mailing list > Use...@li... > https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel > |
From: Richard W. <ri...@no...> - 2018-03-13 13:59:13
|
Am Dienstag, 13. März 2018, 14:24:23 CET schrieb Geert Uytterhoeven: > Hi Richard, > > On Mon, Mar 12, 2018 at 4:21 PM, Richard Weinberger <ri...@no...> wrote: > > Am Montag, 12. März 2018, 16:10:45 CET schrieb Brandeburg, Jesse: > >> > Is the list working for everyone? > >> > >> I got this mail... BTW Sourceforge had a major datacenter issue over the > >> last few weeks, not sure if that broke something along the way. > > > > Hmm, I got this mail only because you CC'ed me. I don't see it in my > > mailinglist inbox. > > > > We should bite the bullet and migrate way from sf.net, finally. > > Any volunteers? > > You can ask DaveM to create a list at vger. Yes, or infradead.org. The bigger problem is migrating all users. Maybe there is a way to extract a list of subscribers from lists.sourceforge.net. Jeff made me project admin some time ago, maybe I can exhume that account. Or we are rude and expect everyone to re-subscribe to the new UML list. That way we might lose 99% of all subscribers but at least the 1% is interested in UML for sure. ;-) Thanks, //richard |
From: Geert U. <ge...@li...> - 2018-03-13 13:24:32
|
Hi Richard, On Mon, Mar 12, 2018 at 4:21 PM, Richard Weinberger <ri...@no...> wrote: > Am Montag, 12. März 2018, 16:10:45 CET schrieb Brandeburg, Jesse: >> > Is the list working for everyone? >> >> I got this mail... BTW Sourceforge had a major datacenter issue over the >> last few weeks, not sure if that broke something along the way. > > Hmm, I got this mail only because you CC'ed me. I don't see it in my > mailinglist inbox. > > We should bite the bullet and migrate way from sf.net, finally. > Any volunteers? You can ask DaveM to create a list at vger. Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@li... In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds |
From: Anton I. <ant...@ko...> - 2018-03-12 15:22:46
|
On 03/12/18 15:10, Brandeburg, Jesse wrote: >> Is the list working for everyone? > I got this mail... BTW Sourceforge had a major datacenter issue over the last few weeks, not sure if that broke something along the way. > > Thanks, I will try to pin it down. A couple of mails where I had the list cc-ed for patches never came back to me. I need to check if they show up in the archive. A. |
From: Richard W. <ri...@no...> - 2018-03-12 15:20:14
|
Anton, Jesse, Am Montag, 12. März 2018, 16:10:45 CET schrieb Brandeburg, Jesse: > > Is the list working for everyone? > > I got this mail... BTW Sourceforge had a major datacenter issue over the > last few weeks, not sure if that broke something along the way. Hmm, I got this mail only because you CC'ed me. I don't see it in my mailinglist inbox. We should bite the bullet and migrate way from sf.net, finally. Any volunteers? Thanks, //richard |
From: Brandeburg, J. <jes...@in...> - 2018-03-12 15:10:57
|
> Is the list working for everyone? I got this mail... BTW Sourceforge had a major datacenter issue over the last few weeks, not sure if that broke something along the way. |
From: Anton I. <ant...@ko...> - 2018-03-11 18:29:58
|
HI all, Is the list working for everyone? I did not get the last two messages I sent to the list. Nothing in the logs on my side either - they were accepted by sourceforge, but no attempts to send them back. A |
From: Richard W. <ri...@no...> - 2018-03-11 11:17:59
|
Am Sonntag, 11. März 2018, 11:55:47 CET schrieb Dominik Brodowski: > do_rmdir() is used in the VFS layer at fs/namei.c, so use a different > name in hostfs. > > CC: Jeff Dike <jd...@ad...> > CC: Richard Weinberger <ri...@no...> > CC: use...@li... > Signed-off-by: Dominik Brodowski <li...@do...> Acked-by: Richard Weinberger <ri...@no...> Thanks, //richard |
From: Andi K. <an...@fi...> - 2018-03-01 05:30:55
|
From: Andi Kleen <ak...@li...> Newer glibc did some include namespace "cleanups" and removed struct ucontext and friends. This already broke a lot of software, and UML seems to be the latest victim. Use the typedefs which are still available. They also work on older glibcs. Signed-off-by: Andi Kleen <ak...@li...> --- arch/um/os-Linux/signal.c | 2 +- arch/x86/um/stub_segv.c | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/arch/um/os-Linux/signal.c b/arch/um/os-Linux/signal.c index a86d7cc2c2d8..a5c0c909c48b 100644 --- a/arch/um/os-Linux/signal.c +++ b/arch/um/os-Linux/signal.c @@ -159,7 +159,7 @@ static void (*handlers[_NSIG])(int sig, struct siginfo *si, mcontext_t *mc) = { static void hard_handler(int sig, siginfo_t *si, void *p) { - struct ucontext *uc = p; + ucontext_t *uc = p; mcontext_t *mc = &uc->uc_mcontext; unsigned long pending = 1UL << sig; diff --git a/arch/x86/um/stub_segv.c b/arch/x86/um/stub_segv.c index 1518d2805ae8..fd6825537b97 100644 --- a/arch/x86/um/stub_segv.c +++ b/arch/x86/um/stub_segv.c @@ -10,7 +10,7 @@ void __attribute__ ((__section__ (".__syscall_stub"))) stub_segv_handler(int sig, siginfo_t *info, void *p) { - struct ucontext *uc = p; + ucontext_t *uc = p; GET_FAULTINFO_FROM_MC(*((struct faultinfo *) STUB_DATA), &uc->uc_mcontext); -- 2.14.3 |
From: Richard W. <ri...@no...> - 2018-02-07 00:18:23
|
Anton, Am Samstag, 27. Januar 2018, 12:42:17 CET schrieb Anton Ivanov: > Thanks, looks correct, +1 > > Richard, can you add it to the next pull. > > Thanks in advance, Is that a Reviewed-by? :) (Same for the other patch) Thanks, //richard P.s: Something is odd with your mail setup, none of your mails made it to the mailinglist. |
From: Jesse B. <jes...@in...> - 2018-02-01 23:36:50
|
Not sure when it got broken, but without this patch the command make ARCH=um defconfig make ARCH=um fails due to struct ucontext being undefined. arch/um/os-Linux/signal.c: In function ‘hard_handler’: arch/um/os-Linux/signal.c:163:22: error: dereferencing pointer to incomplete type ‘struct ucontext’ mcontext_t *mc = &uc->uc_mcontext; <there are two errors like the above> The fix seems fairly simple, that the code just needs to use ucontext_t define instead. I didn't verify that user-mode-linux is working after this change, just that it builds successfully. Cc: Jeff Dike <jd...@ad...> Cc: Richard Weinberger <ri...@no...> Cc: use...@li... Signed-off-by: Jesse Brandeburg <jes...@in...> --- arch/um/os-Linux/signal.c | 2 +- arch/x86/um/stub_segv.c | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/arch/um/os-Linux/signal.c b/arch/um/os-Linux/signal.c index a86d7cc2c2d8..a5c0c909c48b 100644 --- a/arch/um/os-Linux/signal.c +++ b/arch/um/os-Linux/signal.c @@ -159,7 +159,7 @@ static void (*handlers[_NSIG])(int sig, struct siginfo *si, mcontext_t *mc) = { static void hard_handler(int sig, siginfo_t *si, void *p) { - struct ucontext *uc = p; + ucontext_t *uc = p; mcontext_t *mc = &uc->uc_mcontext; unsigned long pending = 1UL << sig; diff --git a/arch/x86/um/stub_segv.c b/arch/x86/um/stub_segv.c index 1518d2805ae8..fd6825537b97 100644 --- a/arch/x86/um/stub_segv.c +++ b/arch/x86/um/stub_segv.c @@ -10,7 +10,7 @@ void __attribute__ ((__section__ (".__syscall_stub"))) stub_segv_handler(int sig, siginfo_t *info, void *p) { - struct ucontext *uc = p; + ucontext_t *uc = p; GET_FAULTINFO_FROM_MC(*((struct faultinfo *) STUB_DATA), &uc->uc_mcontext); -- 2.14.3 |