From: Kees Cook <keescook@chromium.org> To: Oleksandr Natalenko <oleksandr@natalenko.name> Cc: David Windsor <dave@nullcore.net>, "James E.J. Bottomley" <jejb@linux.vnet.ibm.com>, "Martin K. Petersen" <martin.petersen@oracle.com>, linux-scsi@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>, Christoph Hellwig <hch@lst.de>, Jens Axboe <axboe@kernel.dk>, Hannes Reinecke <hare@suse.com>, Johannes Thumshirn <jthumshirn@suse.de>, linux-block@vger.kernel.org, paolo.valente@linaro.org Subject: Re: usercopy whitelist woe in scsi_sense_cache Date: Thu, 12 Apr 2018 15:47:49 -0700 [thread overview] Message-ID: <CAGXu5j+dh1zm32iBjRVh0s+3gLJYgjwt+z1aBJmrK2Cr8XPWnA@mail.gmail.com> (raw) In-Reply-To: <CAGXu5jLSmJv9AstzsgSscrv-wA7FwfrxAKRxj-FVBmihQvnj1g@mail.gmail.com> On Thu, Apr 12, 2018 at 3:01 PM, Kees Cook <keescook@chromium.org> wrote: > On Thu, Apr 12, 2018 at 12:04 PM, Oleksandr Natalenko > <oleksandr@natalenko.name> wrote: >> Hi. >> >> On =C4=8Dtvrtek 12. dubna 2018 20:44:37 CEST Kees Cook wrote: >>> My first bisect attempt gave me commit 5448aca41cd5 ("null_blk: wire >>> up timeouts"), which seems insane given that null_blk isn't even built >>> in the .config. I managed to get the testing automated now for a "git >>> bisect run ...", so I'm restarting again to hopefully get a better >>> answer. Normally the Oops happens in the first minute of running. I've >>> set the timeout to 10 minutes for a "good" run... After fixing up some build issues in the middle of the 4.16 cycle, I get an unhelpful bisect result of commit 0a4b6e2f80aa ("Merge branch 'for-4.16/block'". Instead of letting the test run longer, I'm going to switch to doing several shorter test boots per kernel and see if that helps. One more bisect coming... >> Apparently, you do this on Linus' tree, right? If so, I won't compile it= here >> then. > > Actually, I didn't test Linus's tree, but I can do that after the most > recent bisect finishes... I'm just trying to find where it went wrong > in 4.16. FWIW, I see an Oops under Linus's latest tree. -Kees --=20 Kees Cook Pixel Security
WARNING: multiple messages have this Message-ID (diff)
From: Kees Cook <keescook@chromium.org> To: Oleksandr Natalenko <oleksandr@natalenko.name> Cc: David Windsor <dave@nullcore.net>, "James E.J. Bottomley" <jejb@linux.vnet.ibm.com>, "Martin K. Petersen" <martin.petersen@oracle.com>, linux-scsi@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>, Christoph Hellwig <hch@lst.de>, Jens Axboe <axboe@kernel.dk>, Hannes Reinecke <hare@suse.com>, Johannes Thumshirn <jthumshirn@suse.de>, linux-block@vger.kernel.org, paolo.valente@linaro.org Subject: Re: usercopy whitelist woe in scsi_sense_cache Date: Thu, 12 Apr 2018 15:47:49 -0700 [thread overview] Message-ID: <CAGXu5j+dh1zm32iBjRVh0s+3gLJYgjwt+z1aBJmrK2Cr8XPWnA@mail.gmail.com> (raw) In-Reply-To: <CAGXu5jLSmJv9AstzsgSscrv-wA7FwfrxAKRxj-FVBmihQvnj1g@mail.gmail.com> On Thu, Apr 12, 2018 at 3:01 PM, Kees Cook <keescook@chromium.org> wrote: > On Thu, Apr 12, 2018 at 12:04 PM, Oleksandr Natalenko > <oleksandr@natalenko.name> wrote: >> Hi. >> >> On čtvrtek 12. dubna 2018 20:44:37 CEST Kees Cook wrote: >>> My first bisect attempt gave me commit 5448aca41cd5 ("null_blk: wire >>> up timeouts"), which seems insane given that null_blk isn't even built >>> in the .config. I managed to get the testing automated now for a "git >>> bisect run ...", so I'm restarting again to hopefully get a better >>> answer. Normally the Oops happens in the first minute of running. I've >>> set the timeout to 10 minutes for a "good" run... After fixing up some build issues in the middle of the 4.16 cycle, I get an unhelpful bisect result of commit 0a4b6e2f80aa ("Merge branch 'for-4.16/block'". Instead of letting the test run longer, I'm going to switch to doing several shorter test boots per kernel and see if that helps. One more bisect coming... >> Apparently, you do this on Linus' tree, right? If so, I won't compile it here >> then. > > Actually, I didn't test Linus's tree, but I can do that after the most > recent bisect finishes... I'm just trying to find where it went wrong > in 4.16. FWIW, I see an Oops under Linus's latest tree. -Kees -- Kees Cook Pixel Security
next prev parent reply other threads:[~2018-04-12 22:47 UTC|newest] Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-04-04 19:07 usercopy whitelist woe in scsi_sense_cache Oleksandr Natalenko 2018-04-04 20:21 ` Kees Cook 2018-04-04 20:44 ` Douglas Gilbert 2018-04-04 20:49 ` Oleksandr Natalenko 2018-04-04 21:25 ` Kees Cook 2018-04-04 21:34 ` Oleksandr Natalenko 2018-04-05 9:56 ` Oleksandr Natalenko 2018-04-05 14:21 ` Kees Cook 2018-04-05 14:32 ` Oleksandr Natalenko 2018-04-05 14:33 ` Oleksandr Natalenko [not found] ` <CAGXu5jL8oLV2xvjBVYv_SNXr74LdgpXEmU7K+cLYpD7jh2chgw@mail.gmail.com> 2018-04-05 18:52 ` Kees Cook 2018-04-06 6:21 ` Oleksandr Natalenko 2018-04-08 19:07 ` Oleksandr Natalenko 2018-04-09 9:35 ` Christoph Hellwig 2018-04-09 15:54 ` Oleksandr Natalenko 2018-04-09 18:32 ` Kees Cook 2018-04-09 19:02 ` Oleksandr Natalenko 2018-04-09 20:30 ` Kees Cook 2018-04-09 23:03 ` Kees Cook 2018-04-10 6:35 ` Oleksandr Natalenko 2018-04-10 6:53 ` Kees Cook 2018-04-10 17:16 ` Oleksandr Natalenko 2018-04-11 3:13 ` Kees Cook 2018-04-11 22:47 ` Kees Cook 2018-04-12 0:03 ` Kees Cook 2018-04-12 18:44 ` Kees Cook 2018-04-12 19:04 ` Oleksandr Natalenko 2018-04-12 19:04 ` Oleksandr Natalenko 2018-04-12 22:01 ` Kees Cook 2018-04-12 22:01 ` Kees Cook 2018-04-12 22:47 ` Kees Cook [this message] 2018-04-12 22:47 ` Kees Cook 2018-04-13 3:02 ` Kees Cook 2018-04-16 20:44 ` Kees Cook 2018-04-17 3:12 ` Kees Cook 2018-04-17 9:19 ` Oleksandr Natalenko 2018-04-17 16:25 ` Kees Cook 2018-04-17 10:02 ` James Bottomley 2018-04-17 16:30 ` Kees Cook 2018-04-17 16:42 ` Kees Cook 2018-04-17 16:46 ` Jens Axboe 2018-04-17 20:03 ` Kees Cook 2018-04-17 20:20 ` Kees Cook 2018-04-17 20:25 ` Kees Cook 2018-04-17 20:28 ` Jens Axboe 2018-04-17 20:28 ` Jens Axboe 2018-04-17 20:46 ` Kees Cook 2018-04-17 21:25 ` Kees Cook 2018-04-17 21:39 ` Jens Axboe 2018-04-17 21:47 ` Kees Cook 2018-04-17 21:48 ` Jens Axboe 2018-04-17 22:57 ` Jens Axboe 2018-04-17 23:06 ` Kees Cook 2018-04-17 23:12 ` Jens Axboe 2018-04-18 9:08 ` Paolo Valente 2018-04-18 9:08 ` Paolo Valente 2018-04-18 14:30 ` Jens Axboe 2018-04-19 9:32 ` Paolo Valente 2018-04-19 9:32 ` Paolo Valente 2018-04-20 20:23 ` Kees Cook 2018-04-20 20:41 ` Oleksandr Natalenko 2018-04-21 8:43 ` Paolo Valente 2018-04-21 8:43 ` Paolo Valente 2018-04-17 21:55 ` Oleksandr Natalenko 2018-04-10 13:47 ` Oleksandr Natalenko 2018-04-04 20:32 ` Kees Cook 2018-04-04 20:47 ` Douglas Gilbert
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=CAGXu5j+dh1zm32iBjRVh0s+3gLJYgjwt+z1aBJmrK2Cr8XPWnA@mail.gmail.com \ --to=keescook@chromium.org \ --cc=axboe@kernel.dk \ --cc=dave@nullcore.net \ --cc=hare@suse.com \ --cc=hch@lst.de \ --cc=jejb@linux.vnet.ibm.com \ --cc=jthumshirn@suse.de \ --cc=linux-block@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-scsi@vger.kernel.org \ --cc=martin.petersen@oracle.com \ --cc=oleksandr@natalenko.name \ --cc=paolo.valente@linaro.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: linkBe 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.