public inbox for linux-fsdevel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Bernd Schubert <bernd@bsbernd.com>
Cc: bschubert@ddn.com, joannelkoong@gmail.com,
	linux-fsdevel@vger.kernel.org, miklos@szeredi.hu, neal@gompa.dev
Subject: Re: [GIT PULL] libfuse: run fuse servers as a contained service
Date: Fri, 10 Apr 2026 08:56:01 -0700	[thread overview]
Message-ID: <20260410155601.GS6254@frogsfrogsfrogs> (raw)
In-Reply-To: <549999df-d6eb-43a0-840c-43310de667ca@bsbernd.com>

On Fri, Apr 10, 2026 at 02:24:28PM +0200, Bernd Schubert wrote:
> Hi Darrick,
> 
> On 4/10/26 00:24, Darrick J. Wong wrote:
> > Hi Bernd,
> > 
> > Please pull this branch with changes for libfuse.
> > 
> > As usual, I did a test-merge with the main upstream branch as of a few
> > minutes ago, and didn't see any conflicts.  Please let me know if you
> > encounter any problems.
> 
> I had already merged another patch beginning of this week that
> introduced a new merge conflict in
> .github/workflows/install-ubuntu-dependencies.sh
> 
> I resolved it myself now.
> 
> > 
> > --D
> > 
> > The following changes since commit 3bb9cd99b3688df1bb7536de158ed9e532b277fb:
> > 
> > Add the codechecker/cppcheck github action (2026-04-07 10:08:49 +0200)
> > 
> > are available in the Git repository at:
> > 
> > https://git.kernel.org/pub/scm/linux/kernel/git/djwong/libfuse.git tags/fuse-service-container_2026-04-09
> > 
> > for you to fetch changes up to 0db39a8f8844ff88496ed36da417554cb4f3751d:
> > 
> > nullfs: support fuse systemd service mode (2026-04-09 12:31:08 -0700)
> 
> I had quite a busy last weekend, because I got libfuse security reports.
> In ordert to avoid lots of reports, I just added support for CodeChecker
> + cppcheck and CodeChecker+gcc checker. Clang CTU is is prepared, but I
> need to let AI work over the weekend to fixes for these (obviously will
> need manual editing, as last weekend).
> In the end not too bad and I don't think and urgent need for a new
> release. Although I should probably make a new 3.18.3 version soon.
> 
> That also made me to add new checks. I actually already that github
> codeql checker in place, but only realized last weekend that it didn't
> generate any reports. On your PR that gives
> 
> New alerts in code changed by this pull request
> 
> Security Alerts:
> 
>     4 critical
>     3 high
> 
> Other Alerts:
> 
>     4 warnings
>     10 notes
> 
> 
> Some of these, like "This switch statement should either handle more
> cases, or be rewritten as an if statement." can be suppressed. With some
> I probably agree
> 
> 
> 	cmd = malloc(iov.iov_len);
> 	if (!cmd) {
> 		int error = errno;
> Note
> Declaration hides parameter
> Local variable 'error' hides a parameter of the same name.
> CodeQL

Oh yikes yes.  I probably ought to have added the same "turn the gcc
warnings up real high" patch to my branch that I use for xfs stuff.

(Huh.  No warnings.  Well, that's good at least.)

> The new CodeChecker (gcc,cppchechk) actions also complain, the GUI
> should give the output, but I don't see it yet.

<nod> Any reports you get about my branch, please feel free to lob it at
me and tell me to fix it :)

I can run cppcheck locally, so I'll try to fix all the warnings that
your copy is throwing out, and send you an updated pr.

> My plan for the weekend is to address your comments in my series and
> then to merge it. If still some time left, I would like to fix all the
> reports in your series and merge that as well.
> Then maybe next week to combine some mount code dup that comes from both
> series.
> 
> Ok with you?

Yes, that sounds good.  Let me know if you want any help. :)

--D

> 
> Thanks,
> Bernd

  reply	other threads:[~2026-04-10 15:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-09 22:24 [GIT PULL] libfuse: run fuse servers as a contained service Darrick J. Wong
2026-04-10 12:24 ` Bernd Schubert
2026-04-10 15:56   ` Darrick J. Wong [this message]
2026-04-10 18:30     ` Bernd Schubert
2026-04-10 22:12       ` Darrick J. Wong
2026-04-11  2:48         ` Darrick J. Wong
  -- strict thread matches above, loose matches on Subject: below --
2026-03-04  0:11 Darrick J. Wong
2026-03-04 13:36 ` Bernd Schubert
2026-03-04 17:06   ` Darrick J. Wong
2026-03-04 18:06     ` Darrick J. Wong
2026-03-04 19:29       ` Bernd Schubert
2026-03-04 21:08         ` Darrick J. Wong
2026-03-04 23:23   ` Darrick J. Wong
2026-03-09  2:27     ` Darrick J. Wong
2026-03-09 17:34       ` Bernd Schubert
2026-03-09 18:35         ` Darrick J. Wong

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260410155601.GS6254@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=bernd@bsbernd.com \
    --cc=bschubert@ddn.com \
    --cc=joannelkoong@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=neal@gompa.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox