linux-f2fs-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] [Bug 213877] Mount multiple SMR block devices exceed certain number cause system non-response
Date: Tue, 27 Jul 2021 10:10:06 +0000	[thread overview]
Message-ID: <bug-213877-202145-lZ9gqIWYxe@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-213877-202145@https.bugzilla.kernel.org/>

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

James Z (leftzheng@gmail.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |trivial
     Kernel Version|Linux DT1                   |Linux
                   |5.13.4-200.fc34.x86_64 #1   |5.13.4-200.fc34.x86_64 #1
                   |SMP Tue Jul 20 20:27:29 UTC |SMP Tue Jul 20 20:27:29 UTC
                   |2021 x86_64 x86_64 x86_64   |2021 x86_64 x86_64 x86_64
                   |GNU/Linux                   |GNU/Linux

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

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

_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

  reply	other threads:[~2021-07-27 10:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-27 10:07 [f2fs-dev] [Bug 213877] New: Mount multiple SMR block devices exceed certain number cause system non-response bugzilla-daemon
2021-07-27 10:10 ` bugzilla-daemon [this message]
2021-07-27 16:22 ` [f2fs-dev] [Bug 213877] " bugzilla-daemon
2021-07-30  3:10 ` bugzilla-daemon
2021-07-30  3:26 ` bugzilla-daemon
2021-07-30 10:04 ` bugzilla-daemon
2021-09-04 10:17 ` bugzilla-daemon
2021-09-04 11:43 ` 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-213877-202145-lZ9gqIWYxe@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    /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).