On Thu, Aug 21, 2025 at 03:15:24PM +0300, Vladimir Sementsov-Ogievskiy wrote: > On 20.08.25 16:30, Peter Xu wrote: > > On Wed, Aug 13, 2025 at 07:48:48PM +0300, Vladimir Sementsov-Ogievskiy > > wrote: > > > For migration channel keep fds non-blocking property as is. > > > It's needed for future local migration of fds. > > > > It is pretty risky. This changes the attribute for all the iochannels that > > migration incoming side uses, including multifd / postcopy / ... > > But for now nobody (except CPR-transfer) really pass fds through migration, > and for CPR-transfer it's obviously better to preserve the state by default > (see > my answer in previous patch). > > So I think, we are in a point, where we can chose the good default, and > document it. > > > > > I left comment in previous patch as a pure question trying to understand > > whether the feature is needed. If it is, here it might still be good to: > > > > - Above the line add a comment explaning why > > - Only apply it to whatever channel that matters. In this case, IIUC > > only the main channel matters > > > > I still think that preserving non-blocking flag "as is" is good default for > migration, > please look at my answer in previous patch. However, in this series I may > adopt > to any approach.
I also commented in the previous patch, let's see whether we can make it not only the default for migration, but the default for iochannels (hence, any chance to drop the new feature flag completely..). If that won't fly, I think this is fine. In that case, please explicitly mention that it's intentional to change all iochannels that migration uses in the commit message, and we can also add a comment inline explaining why we set this default for all migration channels. Thanks, -- Peter Xu
