All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 198923] Linux 4.15.4+: Write on Ext4 causes system block
Date: Fri, 08 Nov 2024 12:38:50 +0000	[thread overview]
Message-ID: <bug-198923-11613-SyCXKqV7V1@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-198923-11613@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=198923

JeremyWalsh (jeremywalsh4477@gmail.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jeremywalsh4477@gmail.com

--- Comment #19 from JeremyWalsh (jeremywalsh4477@gmail.com) ---
(In reply to Dennis Busch from comment #6)
> The bug report I linked to in comment 3 mentioned two patches (
> https://patchwork.kernel.org/patch/10181165/ and
> https://patchwork.kernel.org/patch/10233617/ ) but neither of those appears
> to have been applied. I would stick to the last working kernel version for
> now (for me that is 4.14.19 as mentioned in that other bug report) and keep
> an eye on
> https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git/
> https://flappydunkgame.com to
> see if anything familiar looking pops up which suggests that this particular
> problem was fixed ( maybe it already was but I am unable to determine for
> sure as I do not fully understand the issue, just have a hunch the problem
> is/was a locking issue in the RCU system ).

I think so...

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2024-11-08 12:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-198923-11613@https.bugzilla.kernel.org/>
2023-11-08  9:37 ` [Bug 198923] Linux 4.15.4+: Write on Ext4 causes system block bugzilla-daemon
2023-11-11  0:55 ` bugzilla-daemon
2024-01-22  0:33 ` bugzilla-daemon
2024-04-20  7:18 ` bugzilla-daemon
2024-05-13 10:09 ` bugzilla-daemon
2024-05-13 10:49 ` bugzilla-daemon
2024-05-13 23:22 ` bugzilla-daemon
2024-05-21  9:29 ` bugzilla-daemon
2024-06-29 12:15 ` bugzilla-daemon
2024-11-08 12:38 ` bugzilla-daemon [this message]
2025-05-26  4:07 ` bugzilla-daemon
2025-05-26  4:09 ` bugzilla-daemon

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=bug-198923-11613-SyCXKqV7V1@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.