From: Eric Sandeen <email@example.com> To: Eric Sandeen <firstname.lastname@example.org>, Luis Chamberlain <email@example.com>, firstname.lastname@example.org, email@example.com Cc: firstname.lastname@example.org, email@example.com Subject: Re: [PATCH 0/6] sysctl: add pending proc_do_large_bitmap fix Date: Thu, 21 Mar 2019 14:18:32 -0500 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <email@example.com> On 3/21/19 12:13 PM, Eric Sandeen wrote: > On 3/20/19 5:28 PM, Luis Chamberlain wrote: >> Andrew, Kees, >> >> Eric sent a fix out for proc_do_large_bitmap() last month for when >> using a large input buffer. After patch review a test case for the issue >> was built and submitted. I noticed there were a few issues with the >> tests, but instead of just asking Eric to address them I've taken >> care of them and ammended the commit where necessary. There's a >> few issues he reported which I also address and fix in this series. >> >> Since we *do* expect users of these scripts to also use them on older >> kernels, I've also addressed not breaking calling the script for them, >> and gives us an easy way to easily extend our tests cases for future >> kernels as well. >> >> Before anyone considers these for stable as minor fixes, I'd recommend >> we also address the discrepancy on the read side of things: modify the >> test script to use diff against the target file instead of using the >> temp file. >> >> Eric Sandeen (2): >> test_sysctl: add proc_do_large_bitmap() test case >> sysctl: Fix proc_do_large_bitmap for large input buffers > > Isn't this missing: > > [PATCH] sysctl: add proc_do_large_bitmap test node Oh, I see, you rolled it into the test patch. that wasn't clear...
prev parent reply other threads:[~2019-03-21 19:18 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-03-20 22:28 Luis Chamberlain 2019-03-20 22:28 ` [PATCH 1/6] test_sysctl: remove superfluous test_reqs() Luis Chamberlain 2019-03-20 22:28 ` [PATCH 2/6] test_sysctl: load module before testing for it Luis Chamberlain 2019-03-20 22:28 ` [PATCH 3/6] test_sysctl: ignore diff output on verify_diff_w() Luis Chamberlain 2019-03-20 22:28 ` [PATCH 4/6] test_sysctl: allow graceful use on older kernels Luis Chamberlain 2019-03-20 22:28 ` [PATCH 5/6] test_sysctl: add proc_do_large_bitmap() test case Luis Chamberlain 2019-03-20 22:28 ` [PATCH 6/6] sysctl: Fix proc_do_large_bitmap for large input buffers Luis Chamberlain 2019-03-21 16:42 ` [PATCH 0/6] sysctl: add pending proc_do_large_bitmap fix Kees Cook 2019-04-24 17:42 ` Eric Sandeen 2019-04-24 19:05 ` Kees Cook 2019-03-21 17:13 ` Eric Sandeen 2019-03-21 19:18 ` Eric Sandeen [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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [PATCH 0/6] sysctl: add pending proc_do_large_bitmap fix' \ /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
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.