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: Sun, 16 Feb 2020 01:46:49 +0000 [thread overview]
Message-ID: <bug-206443-13602-rJFNsvrcfu@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 #12 from Theodore Tso (tytso@mit.edu) ---
I've posted a proposed improvement[1] to the first proposed patch[2] on LKML.
[1] https://lore.kernel.org/r/20200215233817.GA670792@mit.edu
[2] https://bugzilla.kernel.org/attachment.cgi?id=287189
Suraj, please note that your patches are whitespace damaged, and are lacking
the Developer's Certification of Origin. In the future, it would save me a
lot of time you take a look at the Submitting Patches[3] instructions from the
kernel documentation.
[3] https://www.kernel.org/doc/html/latest/process/submitting-patches.html
You can either use e-mail to linux-ext4@vger.kernel.org or attach patches to a
Bugzilla entry. although the former is certainly preferred. It's better to
send a proposal to the linux-ext4@vger.kernel.org, since that way the patch can
also get tracked via patchwork[4], and on lore.kernel.org, as in [1] above.
[4] http://patchwork.ozlabs.org/project/linux-ext4/list/
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2020-02-16 1:46 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 [this message]
2020-02-19 19:30 ` bugzilla-daemon
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-rJFNsvrcfu@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 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).