From: Christoph Hellwig <hch@lst.de>
To: lkp@lists.01.org
Subject: Re: [block] 9d037ad707: BUG:unable_to_handle_kernel
Date: Thu, 29 Nov 2018 18:05:35 +0100 [thread overview]
Message-ID: <20181129170535.GA28147@lst.de> (raw)
In-Reply-To: <20181129092031.GF21676@shao2-debian>
[-- Attachment #1: Type: text/plain, Size: 405 bytes --]
On Thu, Nov 29, 2018 at 05:20:31PM +0800, kernel test robot wrote:
> FYI, we noticed the following commit (built with gcc-7):
>
> commit: 9d037ad707ed6069fbea4e38e6ee37e027b13f1d ("block: remove req->timeout_list")
> https://git.kernel.org/cgit/linux/kernel/git/axboe/linux-block.git mq-perf
This looks very odd. How could we introduce a new BUG with the removal
of an unused structure member?
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: kernel test robot <rong.a.chen@intel.com>
Cc: Christoph Hellwig <hch@lst.de>, Jens Axboe <axboe@kernel.dk>,
LKML <linux-kernel@vger.kernel.org>, Jens Axboe <axboe@fb.com>,
lkp@01.org
Subject: Re: [LKP] [block] 9d037ad707: BUG:unable_to_handle_kernel
Date: Thu, 29 Nov 2018 18:05:35 +0100 [thread overview]
Message-ID: <20181129170535.GA28147@lst.de> (raw)
In-Reply-To: <20181129092031.GF21676@shao2-debian>
On Thu, Nov 29, 2018 at 05:20:31PM +0800, kernel test robot wrote:
> FYI, we noticed the following commit (built with gcc-7):
>
> commit: 9d037ad707ed6069fbea4e38e6ee37e027b13f1d ("block: remove req->timeout_list")
> https://git.kernel.org/cgit/linux/kernel/git/axboe/linux-block.git mq-perf
This looks very odd. How could we introduce a new BUG with the removal
of an unused structure member?
next prev parent reply other threads:[~2018-11-29 17:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-29 9:20 [block] 9d037ad707: BUG:unable_to_handle_kernel kernel test robot
2018-11-29 9:20 ` [LKP] " kernel test robot
2018-11-29 17:05 ` Christoph Hellwig [this message]
2018-11-29 17:05 ` Christoph Hellwig
2018-11-29 17:10 ` Jens Axboe
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=20181129170535.GA28147@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.