From: Christoph Hellwig <hch@lst.de>
To: lkp@lists.01.org
Subject: Re: [scsi] 6aded12b10: kernel_BUG_at_mm/usercopy.c
Date: Wed, 23 Mar 2022 08:14:10 +0100 [thread overview]
Message-ID: <20220323071409.GA25480@lst.de> (raw)
In-Reply-To: <20220320143453.GD6208@xsang-OptiPlex-9020>
[-- Attachment #1: Type: text/plain, Size: 375 bytes --]
The actual warning is;
[ 34.496096][ T331] usercopy: Kernel memory overwrite attempt detected to spans multiple pages (off set 0, size 6)!
This is for the cmnd field in struct scsi_cmnd, which is allocated by
the block layer as part of the request allocator. So with a specific
packing it can legitimately span pages.
Kees: how can we annotate that this is ok?
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: kernel test robot <oliver.sang@intel.com>
Cc: Christoph Hellwig <hch@lst.de>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Bart Van Assche <bvanassche@acm.org>,
John Garry <john.garry@huawei.com>,
LKML <linux-kernel@vger.kernel.org>,
lkp@lists.01.org, lkp@intel.com,
Kees Cook <keescook@chromium.org>
Subject: Re: [scsi] 6aded12b10: kernel_BUG_at_mm/usercopy.c
Date: Wed, 23 Mar 2022 08:14:10 +0100 [thread overview]
Message-ID: <20220323071409.GA25480@lst.de> (raw)
In-Reply-To: <20220320143453.GD6208@xsang-OptiPlex-9020>
The actual warning is;
[ 34.496096][ T331] usercopy: Kernel memory overwrite attempt detected to spans multiple pages (off set 0, size 6)!
This is for the cmnd field in struct scsi_cmnd, which is allocated by
the block layer as part of the request allocator. So with a specific
packing it can legitimately span pages.
Kees: how can we annotate that this is ok?
next prev parent reply other threads:[~2022-03-23 7:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-20 14:34 [scsi] 6aded12b10: kernel_BUG_at_mm/usercopy.c kernel test robot
2022-03-20 14:34 ` kernel test robot
2022-03-23 7:14 ` Christoph Hellwig [this message]
2022-03-23 7:14 ` Christoph Hellwig
2022-03-23 15:40 ` Kees Cook
2022-03-23 15:40 ` Kees Cook
2022-03-23 15:42 ` Matthew Wilcox
2022-03-23 15:42 ` Matthew Wilcox
2022-03-23 22:30 ` Kees Cook
2022-03-23 22:30 ` Kees Cook
2022-03-23 15:47 ` Christoph Hellwig
2022-03-23 15:47 ` Christoph Hellwig
2022-03-23 22:33 ` Kees Cook
2022-03-23 22:33 ` Kees Cook
2022-03-24 6:48 ` Christoph Hellwig
2022-03-24 6:48 ` Christoph Hellwig
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=20220323071409.GA25480@lst.de \
--to=hch@lst.de \
--cc=lkp@lists.01.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.