v9fs.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: "Linux regression tracking #adding (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: Linux kernel regressions list <regressions@lists.linux.dev>
Cc: v9fs@lists.linux.dev
Subject: Re: fs/9p: regression in 6.8-rc1
Date: Tue, 30 Jan 2024 16:41:12 +0100	[thread overview]
Message-ID: <3f08ca1f-77ac-4636-86d4-52b79d721fae@leemhuis.info> (raw)
In-Reply-To: <ZbQUU6QKmIftKsmo@FV7GG9FTHL>

On 26.01.24 21:21, Eric Van Hensbergen wrote:
> I caught a problem in the new netfs code when running in 9p when running
> with nocache mode.  A regression sweep is turning up a:
>  [ 1084.438387] netfs: Zero-sized write [R=1b6da]
> when running my ldconfig test (included at the end of this)
> it reports:
> /sbin/ldconfig.real: Writing of cache extension data failed: Input/output error
> 
> I will try to dig into this later today if I have time, but not sure I'll get
> to it so I wanted to make other folks aware.  I'm not sure how much other
> elements of my test harness are contributing to reproducing the problem.

To be sure the issue doesn't fall through the cracks unnoticed, I'm
adding it to regzbot, the Linux kernel regression tracking bot:

#regzbot ^introduced v6.7..v6.8-rc1
#regzbot title fs/9p: "netfs: Zero-sized write" failures during ldconfig
test
#regzbot ignore-activity

This isn't a regression? This issue or a fix for it are already
discussed somewhere else? It was fixed already? You want to clarify when
the regression started to happen? Or point out I got the title or
something else totally wrong? Then just reply and tell me -- ideally
while also telling regzbot about it, as explained by the page listed in
the footer of this mail.

Developers: When fixing the issue, remember to add 'Link:' tags pointing
to the report (the parent of this mail). See page linked in footer for
details.

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
That page also explains what to do if mails like this annoy you.

  parent reply	other threads:[~2024-01-30 15:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-26 20:21 fs/9p: regression in 6.8-rc1 Eric Van Hensbergen
2024-01-27  1:53 ` Dominique Martinet
2024-01-28 13:06   ` Dominique Martinet
2024-01-29  9:20   ` David Howells
2024-01-30 15:41 ` Linux regression tracking #adding (Thorsten Leemhuis) [this message]
2024-02-18 10:10   ` Linux regression tracking #update (Thorsten Leemhuis)

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=3f08ca1f-77ac-4636-86d4-52b79d721fae@leemhuis.info \
    --to=regressions@leemhuis.info \
    --cc=regressions@lists.linux.dev \
    --cc=v9fs@lists.linux.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;
as well as URLs for NNTP newsgroup(s).