public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Stephan Wurm <stephan.wurm@a-eberle.de>
To: hch <hch@lst.de>
Cc: Richard Weinberger <richard@nod.at>,
	linux-block <linux-block@vger.kernel.org>,
	Miquel Raynal <miquel.raynal@bootlin.com>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	linux-mtd <linux-mtd@lists.infradead.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Johannes Eigner <johannes.eigner@a-eberle.de>
Subject: Re: ubiblock: null pointer dereference using scatterlist in work_queue
Date: Wed, 9 Aug 2023 16:10:59 +0200	[thread overview]
Message-ID: <ZNOec8JmndA63Mnh@PC-LX-Wurm> (raw)
In-Reply-To: <20230809135308.GA32214@lst.de>

Am 09. Aug 15:53 hat hch geschrieben:
> Well, a scatterlist culd contain a highmem page, in which case sg_virt
> isn't going to cut it and you need to kmap.  Is this a 32-bit system
> with highmem enabled?
I can confirm it is a 32-bit system with highmem enabled.

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

  reply	other threads:[~2023-08-09 14:11 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-17  8:07 ubiblock: null pointer dereference using scatterlist in work_queue Stephan Wurm
2023-07-17  9:42 ` Richard Weinberger
2023-07-17 10:27   ` Stephan Wurm
2023-07-17 11:03     ` Richard Weinberger
2023-07-17 14:55       ` Stephan Wurm
2023-07-17 20:54         ` Richard Weinberger
2023-07-19 14:31         ` Richard Weinberger
2023-07-19 14:38           ` Wurm, Stephan
2023-07-21  7:41             ` Wurm, Stephan
2023-08-07 22:02 ` Richard Weinberger
2023-08-09 13:53   ` hch
2023-08-09 14:10     ` Stephan Wurm [this message]
2023-08-09 14:15       ` hch
2023-08-09 22:34         ` Richard Weinberger
2023-08-09 22:37           ` hch
2023-08-09 22:43             ` Richard Weinberger
2023-08-10 15:43               ` hch

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=ZNOec8JmndA63Mnh@PC-LX-Wurm \
    --to=stephan.wurm@a-eberle.de \
    --cc=hch@lst.de \
    --cc=johannes.eigner@a-eberle.de \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=miquel.raynal@bootlin.com \
    --cc=richard@nod.at \
    --cc=vigneshr@ti.com \
    /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