search for: reapply

..._actions, that I set to a low value for my testings, but then forgot to raise before the migration. As a result, several redirect-only accounts have now their inbox filled with messages that should have been redirected to "real people", then discarded. Would there be a nice way to "reapply" the sieve scripts, so that the messages of those mailboxes are redirected to their final recipients, the way they should have been upon arrival? Many thanks in advance, Axel

...at below. I tracked it back to 4.14-stable, and bisected it there. Why does your virtual machine use a drm driver? Ah, it's a driver for virtual gpu, nice. And if you revert that patch, does everything work again? > # first bad commit: [848dd9bf51544c8e5436960124f3d1f9c51cdb99] drm/qxl: reapply cursor after resetting primary You should also cc: the other developers on that signed-off-by list, like I did here... thanks, greg k-h

...at below. I tracked it back to 4.14-stable, and bisected it there. Why does your virtual machine use a drm driver? Ah, it's a driver for virtual gpu, nice. And if you revert that patch, does everything work again? > # first bad commit: [848dd9bf51544c8e5436960124f3d1f9c51cdb99] drm/qxl: reapply cursor after resetting primary You should also cc: the other developers on that signed-off-by list, like I did here... thanks, greg k-h

On Sun, 2018-06-17 at 11:36 +0200, Greg KH wrote: > > And if you revert that patch, does everything work again? Yes. -Mike

On Sun, Jun 17, 2018 at 12:38:06PM +0200, Mike Galbraith wrote: > On Sun, 2018-06-17 at 11:36 +0200, Greg KH wrote: > > > > And if you revert that patch, does everything work again? > > Yes. Great, Dave, care to revert this in 4.18 so I can queue up that revert in older kernels as well? thanks, greg k-h

On 17 June 2018 at 21:02, Greg KH <gregkh at linuxfoundation.org> wrote: > On Sun, Jun 17, 2018 at 12:38:06PM +0200, Mike Galbraith wrote: >> On Sun, 2018-06-17 at 11:36 +0200, Greg KH wrote: >> > >> > And if you revert that patch, does everything work again? >> >> Yes. > > Great, Dave, care to revert this in 4.18 so I can queue up that revert

On Sun, Jun 17, 2018 at 12:38:06PM +0200, Mike Galbraith wrote: > On Sun, 2018-06-17 at 11:36 +0200, Greg KH wrote: > > > > And if you revert that patch, does everything work again? > > Yes. Great, Dave, care to revert this in 4.18 so I can queue up that revert in older kernels as well? thanks, greg k-h

...uld be >> > something like binary size change that caused different code alignment >> > or some such >> > and which triggered a latent memory bug somewhere else. >> > >> > It's already late evening for you now. Will you have a chance to >> > reapply changes today? >> > >> > --kcc >> > >> >> >> >> On Nov 14, 2013, at 10:15 PM, Kostya Serebryany <kcc at google.com> >> wrote: >> >> >> >>> On Fri, Nov 15, 2013 at 10:14 AM, Bob Wilson <bob.wilson at apple.c...

...only hypothesis is some sort of memory corruption. >>>> >>>> I will keep you posted. >>>> >>>> On Nov 14, 2013, at 9:22 PM, Kostya Serebryany <kcc at google.com> wrote: >>>> >>>>> Also, when are you planing to "reapply the changes or help debug"? >>>>> >>>>> On Fri, Nov 15, 2013 at 9:15 AM, Kostya Serebryany <kcc at google.com> wrote: >>>>>> On Fri, Nov 15, 2013 at 7:26 AM, Bob Wilson <bob.wilson at apple.com> wrote: >>>>>>> Hi...

...igger the failures it could be > > something like binary size change that caused different code alignment > > or some such > > and which triggered a latent memory bug somewhere else. > > > > It's already late evening for you now. Will you have a chance to > > reapply changes today? > > > > --kcc > > > >> > >> On Nov 14, 2013, at 10:15 PM, Kostya Serebryany <kcc at google.com> wrote: > >> > >>> On Fri, Nov 15, 2013 at 10:14 AM, Bob Wilson <bob.wilson at apple.com> wrote: > >>>> T...

..., if my commits did indeed trigger the failures it could be > something like binary size change that caused different code alignment > or some such > and which triggered a latent memory bug somewhere else. > > It's already late evening for you now. Will you have a chance to > reapply changes today? > > --kcc > >> >> On Nov 14, 2013, at 10:15 PM, Kostya Serebryany <kcc at google.com> wrote: >> >>> On Fri, Nov 15, 2013 at 10:14 AM, Bob Wilson <bob.wilson at apple.com> wrote: >>>> The bit code file produced by the sta...

...o, not that I am aware of. So, if my commits did indeed trigger the failures it could be something like binary size change that caused different code alignment or some such and which triggered a latent memory bug somewhere else. It's already late evening for you now. Will you have a chance to reapply changes today? --kcc > > On Nov 14, 2013, at 10:15 PM, Kostya Serebryany <kcc at google.com> wrote: > >> On Fri, Nov 15, 2013 at 10:14 AM, Bob Wilson <bob.wilson at apple.com> wrote: >>> The bit code file produced by the stage 1 compiler for one of the files in...

Let's say I have some iptables rules defined to restrict guest traffic. If I restart the hosts firewall 'service iptables restart', all the guest-specific rules get blown away. Is there a way to reapply all the guest firewall rules, without restarting each individual guest? It looks like if I edit a nwfilter with `virsh nwfilter-edit` it goes and reapplies the rules to all the guests, so this functionality seems to be present already.

...his point, and I share your puzzlement about how your changes could possibly break the compiler. My only hypothesis is some sort of memory corruption. I will keep you posted. On Nov 14, 2013, at 9:22 PM, Kostya Serebryany <kcc at google.com> wrote: > Also, when are you planing to "reapply the changes or help debug"? > > On Fri, Nov 15, 2013 at 9:15 AM, Kostya Serebryany <kcc at google.com> wrote: >> On Fri, Nov 15, 2013 at 7:26 AM, Bob Wilson <bob.wilson at apple.com> wrote: >>> Hi Kostya, >>> >>> Thanks for the heads-up on t...

...like these patches may be breaking our > bootstrapped LTO build. Our buildbots have been failing all day, and we’re > still trying to figure out the problem. I’m going to speculatively revert > those changes, since they were the only patches on the buildbot blame list. > I will either reapply the changes or help debug the problem. How could this possibly affect your LTO build? The option is off by default. Do you have any details, logs, etc? > > —Bob > > On Nov 14, 2013, at 5:42 AM, Kostya Serebryany <kcc at google.com> wrote: > > Bob, Justin, > > I'v...

Ok. I'm configuring my iptables scripts so that specific iptables rules for virtual network interfaces used for tinc go on tinc-up-fw and tinc-down-fw custom scripts. When I reload iptables rules manually to apply changes iptables scripts flush all chains and reapply rules and now also search in /etc/tinc/<netname>/ directories if the related virtual network interface is up and running and if so it reapply every tinc-up-fw, so probably we do not need anymore a persistent tun virtual interface ever up. Has tinc possibility to pass a custom env veriable l...

...changes could possibly break the compiler. My only hypothesis is some sort of memory corruption. >> >> I will keep you posted. >> >> On Nov 14, 2013, at 9:22 PM, Kostya Serebryany <kcc at google.com> wrote: >> >>> Also, when are you planing to "reapply the changes or help debug"? >>> >>> On Fri, Nov 15, 2013 at 9:15 AM, Kostya Serebryany <kcc at google.com> wrote: >>>> On Fri, Nov 15, 2013 at 7:26 AM, Bob Wilson <bob.wilson at apple.com> wrote: >>>>> Hi Kostya, >>>>> &...

...igger the failures it could be > > something like binary size change that caused different code alignment > > or some such > > and which triggered a latent memory bug somewhere else. > > > > It's already late evening for you now. Will you have a chance to > > reapply changes today? > > > > --kcc > > > >> > >> On Nov 14, 2013, at 10:15 PM, Kostya Serebryany <kcc at google.com> wrote: > >> > >>> On Fri, Nov 15, 2013 at 10:14 AM, Bob Wilson <bob.wilson at apple.com> > wrote: > >>>&...

Also, when are you planing to "reapply the changes or help debug"? On Fri, Nov 15, 2013 at 9:15 AM, Kostya Serebryany <kcc at google.com> wrote: > On Fri, Nov 15, 2013 at 7:26 AM, Bob Wilson <bob.wilson at apple.com> wrote: >> Hi Kostya, >> >> Thanks for the heads-up on this. I haven’t had a chanc...

Your reasoning sounds correct to me. Let's revert for now? I don't think there is an easy fix, we'll have to do a global "must be executed" analysis to reapply the patch soundly. And that's difficult since any external functional call can call "exit(0)". -- Sanjoy On Thu, Sep 26, 2019 at 6:19 AM Tim Northover <t.p.northover at gmail.com> wrote: > > Thanks for the information everyone, it's clarified my thinking > signif...