linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-xfs@vger.kernel.org
Subject: [Bug 204015] BUG: KASAN: slab-out-of-bounds in __bio_add_page+0x1ec/0x2b0
Date: Sat, 29 Jun 2019 14:17:02 +0000	[thread overview]
Message-ID: <bug-204015-201763-lkIYczLWoS@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-204015-201763@https.bugzilla.kernel.org/>

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

--- Comment #2 from Zorro Lang (zlang@redhat.com) ---
(In reply to Darrick J. Wong from comment #1)
> I suspect this is fixed by "xfs: fix iclog allocation size" which will be in
> for-next soon.

Great, I'll verify that after the patch be merged.

-- 
You are receiving this mail because:
You are watching someone on the CC list of the bug.

      parent reply	other threads:[~2019-06-29 14:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-28 14:26 [Bug 204015] New: BUG: KASAN: slab-out-of-bounds in __bio_add_page+0x1ec/0x2b0 bugzilla-daemon
2019-06-28 20:52 ` [Bug 204015] " bugzilla-daemon
2019-06-29 14:17 ` bugzilla-daemon [this message]

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-204015-201763-lkIYczLWoS@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-xfs@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).