From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.8 required=3.0 tests=BAYES_00,DKIM_INVALID, DKIM_SIGNED,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 55268C433E0 for ; Wed, 5 Aug 2020 19:51:55 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 3475520842 for ; Wed, 5 Aug 2020 19:51:55 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="key not found in DNS" (0-bit key) header.d=szeredi.hu header.i=@szeredi.hu header.b="fHDQmOPF" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728175AbgHETvw (ORCPT ); Wed, 5 Aug 2020 15:51:52 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:47400 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728155AbgHEQwO (ORCPT ); Wed, 5 Aug 2020 12:52:14 -0400 Received: from mail-ej1-x644.google.com (mail-ej1-x644.google.com [IPv6:2a00:1450:4864:20::644]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5D2EEC034609 for ; Wed, 5 Aug 2020 04:56:15 -0700 (PDT) Received: by mail-ej1-x644.google.com with SMTP id d6so32242085ejr.5 for ; Wed, 05 Aug 2020 04:56:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=szeredi.hu; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=EFzCfSOy2IvutgdDhPs5RnGz6j56czFjRkJZIjDwC5E=; b=fHDQmOPFaJvbXbvEliSuXqTAPHK8v552b9np6X9cWK6tTGWtQJ8LY3S0vJn2HS00rJ gVpdofbnaxr9+tJ+Mqj1cFGgRzfxwqq+vkUzACPs5rGvCTBqKNfOo+qeWAS+wlxzEwx6 SKI85B2YDPDIN9J5DECiCM+0m7oOnfVCzXQdk= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=EFzCfSOy2IvutgdDhPs5RnGz6j56czFjRkJZIjDwC5E=; b=CVytCGN6Qk2SZWpnJY50eu+pZkcHKPY2Iw4WeywKEY680nRnSvxWA9Pjpw7qfejzkX o5M2MVv8Q1YP9AeW2JCeM4ffLm9MqkvYmTKvbpdzpGywJ9iQdRVPd0Z10S+MnDG7v6JC N3z0AITSbYkhO0tHKd/CAgxpLKZFAIi/9vj3IYdhWJPvziC1qdLepOAejcVAI7mfzoL5 s/3u6BEi2Ow7rt5MISGUM2IV1HyzdjF+Tbgf4CcWAzSn6LW0SbRYCdmbYbZbHuCvufFl TtwvjTffaV83KXwVzNfrHhLNjwbYTbZ142CWIg07tni61TdzEramjUqsVkwJoLy0Kof9 WU0Q== X-Gm-Message-State: AOAM530/YTOigLyBRNCWT/xIWVkQFCm1h2OVNXKth3GeX3OxJ//l1N5Y 7lPxTYC+8bOvZFt93K0qu/VmgXNfKLO8g4FnTO+q0w== X-Google-Smtp-Source: ABdhPJwmuCMEiB1hUFa5v+mcjhs87JwPL8sH9pgCYuW0w9XS34zg5ONW/347iIy+Lf6dRHfU4LRWES4+b7uEih/9ov0= X-Received: by 2002:a17:906:22c1:: with SMTP id q1mr2735858eja.443.1596628572819; Wed, 05 Aug 2020 04:56:12 -0700 (PDT) MIME-Version: 1.0 References: <158454378820.2863966.10496767254293183123.stgit@warthog.procyon.org.uk> <158454391302.2863966.1884682840541676280.stgit@warthog.procyon.org.uk> <1293241.1595501326@warthog.procyon.org.uk> <43c061d26ddef2aa3ca1ac726da7db9ab461e7be.camel@themaw.net> <013e9bb3cb1536c73a5b58c5ff000b3b00629561.camel@themaw.net> In-Reply-To: <013e9bb3cb1536c73a5b58c5ff000b3b00629561.camel@themaw.net> From: Miklos Szeredi Date: Wed, 5 Aug 2020 13:56:01 +0200 Message-ID: Subject: Re: [PATCH 13/17] watch_queue: Implement mount topology and attribute change notifications [ver #5] To: Ian Kent Cc: David Howells , Linus Torvalds , Al Viro , Casey Schaufler , Stephen Smalley , Nicolas Dichtel , Christian Brauner , andres@anarazel.de, Jeff Layton , dray@redhat.com, Karel Zak , keyrings@vger.kernel.org, Linux API , linux-fsdevel@vger.kernel.org, LSM , linux-kernel@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Sender: linux-api-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-api@vger.kernel.org On Wed, Aug 5, 2020 at 1:36 PM Ian Kent wrote: > > I can see in the kernel code that an error is returned if the message > buffer is full when trying to add a message, I just can't see where > to get it in the libmount code. > > That's not really a communication protocol problem. > > Still I need to work out how to detect it, maybe it is seen by > the code in libmount already and I simply can't see what I need > to do to recognise it ... > > So I'm stuck wanting to verify I have got everything that was > sent and am having trouble moving on from that. This is the commit that should add the overrun detection capability: e7d553d69cf6 ("pipe: Add notification lossage handling") Thanks, Miklos