From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 206443] general protection fault in ext4 during simultaneous online resize and write operations
Date: Wed, 19 Feb 2020 19:30:40 +0000 [thread overview]
Message-ID: <bug-206443-13602-ea4oG9eV9i@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-206443-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=206443
--- Comment #13 from Suraj (surajjs@amazon.com) ---
Your approach using call_rcu is very similar to something I was also exploring
so that looks good to me.
Apologies, I didn't realise that patches attached to the BZ had to be mailing
list ready.
There is also the same issue present with the resizing of the s_group_info and
s_flex_groups arrays which are addressed in the following patches which I have
posted to the EXT4 mailing list:
[1/3] ext4: introduce macro sbi_array_rcu_deref() to access rcu protected
fields [1]
[2/3] ext4: fix potential race between s_group_info online resizing and access
[2]
[3/3] ext4: fix potential race between s_flex_groups online resizing and access
[3]
[1] http://patchwork.ozlabs.org/patch/1240507/
[2] http://patchwork.ozlabs.org/patch/1240506/
[3] http://patchwork.ozlabs.org/patch/1240509/
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2020-02-19 19:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-06 19:16 [Bug 206443] New: general protection fault in ext4 during simultaneous online resize and write operations bugzilla-daemon
2020-02-06 19:17 ` [Bug 206443] " bugzilla-daemon
2020-02-06 19:19 ` bugzilla-daemon
2020-02-06 19:19 ` bugzilla-daemon
2020-02-06 19:20 ` bugzilla-daemon
2020-02-06 19:21 ` bugzilla-daemon
2020-02-06 19:25 ` bugzilla-daemon
2020-02-07 6:05 ` bugzilla-daemon
2020-02-07 23:22 ` bugzilla-daemon
2020-02-07 23:22 ` bugzilla-daemon
2020-02-07 23:23 ` bugzilla-daemon
2020-02-15 20:43 ` bugzilla-daemon
2020-02-16 1:46 ` bugzilla-daemon
2020-02-19 19:30 ` bugzilla-daemon [this message]
2020-02-20 4:26 ` 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-206443-13602-ea4oG9eV9i@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@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.